Re: Hard-limits for kern.maxproc
Re: Hard-limits for kern.maxproc
- Subject: Re: Hard-limits for kern.maxproc
- From: Steve Checkoway <email@hidden>
- Date: Fri, 6 Feb 2009 12:06:00 -0800
On Feb 6, 2009, at 11:50 AM, Andrew Gallatin wrote:
Steve Checkoway wrote:
>
> number could be dynamic too, when the system is running low on
memory,
> start returning EAGAIN to fork() calls.
What about kernel call chains that need to succeed? (like allocating
data structures required for disk writes, which in turn are required
to page something out and free memory).
Clearly enough memory would have to be reserved in order to do that
(and other things). I wasn't suggesting waiting until there was no
more memory before it starts to return EAGAIN.
--
Steve Checkoway
"Anyone who says that the solution is to educate the users
hasn't ever met an actual user." -- Bruce Schneier
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden