From: "Manfred Spraul" <manfred@colorfullife.com>
To: "Chris Evans" <chris@scary.beasts.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: system hang with "__alloc_page: 1-order allocation failed"
Date: Tue, 13 Mar 2001 23:45:25 +0100 [thread overview]
Message-ID: <000701c0ac0f$67425060$5517fea9@local> (raw)
In-Reply-To: <Pine.LNX.4.30.0103132128110.20010-100000@ferret.lmh.ox.ac.uk>
From: "Chris Evans" <chris@scary.beasts.org>
>
> I thought (on Intel) there was a 4092 hard limit?
>
That's the 2.2 limit, it's gone.
The new limit is total memory and pid space. The pid's are intentionally
limited to 15 bits, the remaining bits are reserved.
In the worst case one running process can block 3 pid values (one for
the session, one for the process group, one for process id), thus
~11.000 running processes can exhaust the pid space.
--
Manfred
next prev parent reply other threads:[~2001-03-13 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 18:39 system hang with "__alloc_page: 1-order allocation failed" Manfred Spraul
2001-03-13 21:28 ` Chris Evans
2001-03-13 22:45 ` Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-13 1:40 David Shoon
2001-03-13 10:50 ` Mike Galbraith
2001-03-13 13:03 ` Rik van Riel
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='000701c0ac0f$67425060$5517fea9@local' \
--to=manfred@colorfullife.com \
--cc=chris@scary.beasts.org \
--cc=linux-kernel@vger.kernel.org \
/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