Jason Thorpe wrote: > > > There is a lot of hidden 'potential' VM that you haven't considered. > > For example, if the resource limit for a process's stack is 8MB, then > > the process can potentially allocate 8MB of stack even though it may > > actually only allocate 32K of stack. When a process forks, the child > > ...um, so, make the code that deals with faulting in the stack a bit smarter. Uh? Like what? Like overcommitting, for instance? The beauty of overcommitting is that either you do it or you don't. :-) -- Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Would you like to go out with me?" "I'd love to." "Oh, well, n... err... would you?... ahh... huh... what do I do next?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) David Brownlee
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Robert Elz
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Daniel C. Sobral
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Daniel C. Sobral
- Re: Replacement for grep(1) (part 2) David Brownlee
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) David Greenman
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Mike Smith
- Re: Replacement for grep(1) (part 2) Daniel C. Sobral