From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
Willy Tarreau <w@1wt.eu>, Irfan Habib <irfan.habib@gmail.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Maximum number of processes in Linux
Date: Wed, 16 Aug 2006 12:58:59 +0100 [thread overview]
Message-ID: <200608161258.59646.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <44E2ED07.6070203@aitel.hist.no>
On Wednesday 16 August 2006 11:01, Helge Hafting wrote:
> linux-os (Dick Johnson) wrote:
> > Yep....
> >
> > #include <stdio.h>
> > #include <signal.h>
> > int main()
> > {
> > unsigned long i;
> > for(i = 0; ; i++)
> > {
> > switch(fork())
> > {
> > case 0: // kid
> > pause();
> > break;
> > case -1: // Failed
> > printf("%lu\n", i);
> > kill(0, SIGTERM);
> > exit(0);
> > default:
> > break;
> > }
> > }
> > return 0;
> > }
> >
> > Shows a consistent 6140.
>
> Doesn't work here. Without ulimit, I wasn't surprised
> about the resulting OOM mess.
>
> Problem was, it never stopped. I expected OOM to kill
> this program, and quite possibly lots of other running programs
> as well. What I got, was ever-rolling OOM messages
> with stack traces inbetween.
> 2.6.18-rc4-mm1 never recovered and had to be killed by sysrq.
It took 4.5 minutes to recover on my X2 3800+, 2GB RAM, 512MB swap, when I
tried without ulimit on 2.6.18-rc4. However, the OOM killer did call all of
the offending processes and I was able to use the machine for many hours
afterwards. The VM didn't even mind after a swapoff -a.
Maybe an -mm patch?
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-08-16 11:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 17:59 Irfan Habib
2006-08-15 18:12 ` Stephen Hemminger
2006-08-15 18:22 ` linux-os (Dick Johnson)
2006-08-15 18:22 ` Willy Tarreau
2006-08-15 19:01 ` linux-os (Dick Johnson)
2006-08-15 19:13 ` linux-os (Dick Johnson)
2006-08-15 19:13 ` Willy Tarreau
2006-08-15 19:19 ` Arjan van de Ven
2006-08-15 19:26 ` Irfan Habib
2006-08-15 21:50 ` Avi Kivity
2006-08-16 10:01 ` Helge Hafting
2006-08-16 11:33 ` linux-os (Dick Johnson)
2006-08-17 8:00 ` Mike Galbraith
2006-08-16 11:58 ` Alistair John Strachan [this message]
2006-08-15 18:29 ` linux-os (Dick Johnson)
2006-08-15 18:37 ` Alan Cox
2006-08-15 21:00 ` Valdis.Kletnieks
[not found] <fa.evUDdOgjejpeNWKvgan3aKFF880@ifi.uio.no>
2006-08-15 23:12 ` Robert Hancock
2006-08-15 23:39 ` Michael Buesch
2006-08-16 0:04 ` Lee Revell
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=200608161258.59646.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=helge.hafting@aitel.hist.no \
--cc=irfan.habib@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®