mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: 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: Tue, 15 Aug 2006 21:19:44 +0200	[thread overview]
Message-ID: <1155669584.3011.178.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0608151511310.3138@chaos.analogic.com>


> Shows a consistent 6140.
> 

the default limit in proc scales with memory (to avoid really bad
stuff), you can oversize it to 2^16 if you want. 

Going over 2^16 is not too good an idea (16 bit counters overflow),
especially if you have hostile users (read: students) on the machine,
since this is the kind of scenario you can trigger on purpose.



  parent reply	other threads:[~2006-08-15 19:20 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 [this message]
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
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=1155669584.3011.178.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --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®