Messages in this thread | | | Date | Tue, 21 Feb 2006 12:22:44 +0100 | From | Herbert Poetzl <> | Subject | Re: pid_t range question |
| |
On Fri, Feb 17, 2006 at 02:39:55PM -0700, Eric W. Biederman wrote: > David Lang <dlang@digitalinsight.com> writes: > > > I agree that the mojority of users don't hit this limit, but I've > > got a couple of boxes that push it (they run out of ram before that, > > but more ram is on order). > > > > however it sounds like switching to a 64 bit kernel will avoid this > > limit, so I'll put my efforts into configuring a box to do that. > > That is what I would recommend. Unless you do something weird an > painful like configure a kernel doing the 4G/4G split a 32bit box is > going to have memory problems with more than 32K tasks.
or configure the newly introduced 2.13/1.87 (or 1/3 split)
I don't think low memory is really the issue here, the scheduling of 32k+ tasks is much more a problem ...
best, Herbert
> Just remember you need push up /proc/sys/kernel/pid-max to raise the > default on a 64bit box. > > Eric > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |