mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: David Lang <dlang@digitalinsight.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	"linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: pid_t range question
Date: Fri, 17 Feb 2006 14:39:55 -0700	[thread overview]
Message-ID: <m17j7toeac.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0602171201020.8348@qynat.qvtvafvgr.pbz> (David Lang's message of "Fri, 17 Feb 2006 13:20:36 -0800 (PST)")

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.

Just remember you need push up /proc/sys/kernel/pid-max to raise the default
on a 64bit box.

Eric

  reply	other threads:[~2006-02-17 21:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 16:23 linux-os (Dick Johnson)
2006-02-07 22:16 ` Eric W. Biederman
2006-02-08  0:19   ` Ulrich Drepper
2006-02-08  2:39     ` Eric W. Biederman
2006-02-09 16:58   ` Jan Engelhardt
2006-02-09 18:11     ` Eric W. Biederman
2006-02-09 20:13       ` Jesper Juhl
2006-02-10 13:21         ` Jan Engelhardt
2006-02-15 20:40           ` David Lang
2006-02-15 21:00             ` Eric W. Biederman
2006-02-17 16:38             ` Jan Engelhardt
2006-02-17 21:20               ` David Lang
2006-02-17 21:39                 ` Eric W. Biederman [this message]
2006-02-21 11:22                   ` Herbert Poetzl
     [not found] <5DDTr-6Lw-43@gated-at.bofh.it>
     [not found] ` <5DJlY-6J8-29@gated-at.bofh.it>
     [not found]   ` <5EnCK-7Qt-9@gated-at.bofh.it>
     [not found]     ` <5Eoz4-PV-21@gated-at.bofh.it>
     [not found]       ` <5Eqr8-3To-13@gated-at.bofh.it>
2006-02-10  1:19         ` Bodo Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m17j7toeac.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=dlang@digitalinsight.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome