From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: Finn Arne Gangstad <finnag@guardian.no>
Cc: Linus Torvalds <torvalds@transmeta.com>,
"Stephen C. Tweedie" <sct@dcs.ed.ac.uk>,
linux-mm <linux-mm@kvack.org>
Subject: Re: 2.1.90 dies with many procs procs, partial fix
Date: Mon, 23 Mar 1998 20:39:26 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.980323203732.771G-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.3.95.980322022425.5774A-100000@lucifer.guardian.no>
On Sun, 22 Mar 1998, Finn Arne Gangstad wrote:
> int main() {
> int procs = 0;
> while (1) {
> int err = fork();
> if (err == -1) {
> perror("fork failed. eek.");
> exit(EXIT_FAILURE);
> } else if (err == 0) {
> setsid();
> pause();
> _exit(EXIT_SUCCESS);
> }
> ++procs;
> printf("%d children forked off\n", procs);
> usleep(30000);
> }
> exit(EXIT_SUCCESS);
> }
Hmm, this is evidence that I was right when I said
that the free_memory_available() system combined
with our current allocation scheme gives trouble.
Linus, what fix do you propose?
(I don't really feel like coding a fix that will
be rejected :-)
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.fys.ruu.nl/~riel/ | <H.H.vanRiel@fys.ruu.nl> |
+-------------------------------------------+--------------------------+
next parent reply other threads:[~1998-03-23 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.3.95.980322022425.5774A-100000@lucifer.guardian.no>
1998-03-23 19:39 ` Rik van Riel [this message]
1998-03-23 21:20 ` Benjamin C.R. LaHaise
1998-03-23 23:11 ` Linus Torvalds
1998-03-24 9:48 ` 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=Pine.LNX.3.91.980323203732.771G-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=finnag@guardian.no \
--cc=linux-mm@kvack.org \
--cc=sct@dcs.ed.ac.uk \
--cc=torvalds@transmeta.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