From: Uman <a.lahun@editec-lotteries.com>
To: linux-mm@kvack.org
Subject: limit for number of processes
Date: Tue, 17 Apr 2001 12:58:12 +0200 [thread overview]
Message-ID: <3ADC21C4.3000807@editec-lotteries.com> (raw)
In-Reply-To: 200104121659.f3CGxX714605@tuttle.kansas.net
hello.
Yesterday when i wrote program which use fork for every connection, and
made stupid mistake. So i tested my PC(kernel 2.4.3-pre2+xfs) with
something like
while(1){
fork();
}
i had ulimit 4000 processes but my box became completely unresponsible
in X.
As i understood it started to use swap intensively . But amount of
memory was enough
so no OOM killing. The only thing i could do is to reboot.
After testing i found that if i create up to 3200 processes i still can
Ctrl-C and everything
will be good. If i have more i can kill them but kernel threads , as i
understand, continue
to thrash system and the only thing i can do Sys-Rq.
So my question is , what is amount of processes kernel can support (if
i have enough memory)
without thrashing my system and requiring reboot for normal job.
Thank you.
Andrei.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
prev parent reply other threads:[~2001-04-17 10:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 16:58 [PATCH] a simple OOM killer to save me from Netscape Slats Grobnik
2001-04-12 18:25 ` Rik van Riel
2001-04-12 18:49 ` James A. Sutherland
2001-04-13 6:45 ` Eric W. Biederman
2001-04-13 16:20 ` Rik van Riel
2001-04-14 1:20 ` Stephen C. Tweedie
2001-04-16 21:06 ` James A. Sutherland
2001-04-16 21:40 ` Jonathan Morton
2001-04-16 22:12 ` Rik van Riel
2001-04-16 22:21 ` James A. Sutherland
2001-04-17 14:26 ` Jonathan Morton
2001-04-17 19:53 ` Rik van Riel
2001-04-17 20:44 ` James A. Sutherland
2001-04-17 20:59 ` Jonathan Morton
2001-04-17 21:09 ` James A. Sutherland
2001-04-14 7:00 ` Eric W. Biederman
2001-04-15 5:05 ` Rik van Riel
2001-04-15 5:20 ` Rik van Riel
2001-04-16 11:52 ` Szabolcs Szakacsits
2001-04-16 12:17 ` suspend processes at load (was Re: a simple OOM ...) Szabolcs Szakacsits
2001-04-17 19:48 ` Rik van Riel
2001-04-18 21:32 ` Szabolcs Szakacsits
2001-04-18 20:38 ` James A. Sutherland
2001-04-18 23:25 ` Szabolcs Szakacsits
2001-04-18 22:29 ` Rik van Riel
2001-04-19 10:14 ` Stephen C. Tweedie
2001-04-19 13:23 ` Szabolcs Szakacsits
2001-04-19 2:11 ` Rik van Riel
2001-04-19 7:08 ` James A. Sutherland
2001-04-19 13:37 ` Szabolcs Szakacsits
2001-04-19 12:26 ` Christoph Rohland
2001-04-19 12:30 ` James A. Sutherland
2001-04-19 9:15 ` James A. Sutherland
2001-04-19 18:34 ` Dave McCracken
2001-04-19 18:47 ` James A. Sutherland
2001-04-19 18:53 ` Dave McCracken
2001-04-19 19:10 ` James A. Sutherland
2001-04-20 14:58 ` Rik van Riel
2001-04-21 6:10 ` James A. Sutherland
2001-04-19 19:13 ` Rik van Riel
2001-04-19 19:47 ` Gerrit Huizenga
2001-04-20 12:44 ` Szabolcs Szakacsits
2001-04-19 20:06 ` James A. Sutherland
2001-04-20 12:29 ` Szabolcs Szakacsits
2001-04-20 11:50 ` Jonathan Morton
2001-04-20 13:32 ` Szabolcs Szakacsits
2001-04-20 14:30 ` Rik van Riel
2001-04-22 10:21 ` James A. Sutherland
2001-04-20 12:25 ` Szabolcs Szakacsits
2001-04-21 6:08 ` James A. Sutherland
2001-04-20 12:18 ` Szabolcs Szakacsits
2001-04-22 10:19 ` James A. Sutherland
2001-04-17 10:58 ` Uman [this message]
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=3ADC21C4.3000807@editec-lotteries.com \
--to=a.lahun@editec-lotteries.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.