All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg KH <gregkh@suse.de>, Rik van Riel <riel@redhat.com>,
	John Stoffel <john@stoffel.org>, Hedi Berriche <hedi@sgi.com>,
	Mike Travis <travis@sgi.com>, Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jack Steiner <steiner@sgi.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Robin Holt <holt@sgi.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 1/1] init: Provide a kernel start parameter to increase pid_max v2
Date: Thu, 22 Apr 2010 08:57:42 -0500	[thread overview]
Message-ID: <20100422135742.GQ4920@sgi.com> (raw)
In-Reply-To: <20100422102852.72837494@lxorguk.ukuu.org.uk>

> No - to start with it would be far saner for everything involved if the
> 4096 processor minority fixed it for the moment in their arch code by
> doing something like
> 
> 	if (max_pids < PIDS_PER_CPU * num_cpus) {
> 		max_pids = ...
> 		printk(something informative)
> 	}
> 
> in their __init marked code.

I don't understand how it would be possible for the arch maintainers
to predict what a particular machine's configuration would need for
PIDS_PER_CPU.  Many of the extra pids needed on a per-cpu basis are
brought in by device drivers or subsystems.

Are you proposing a typical configuration be used for the basis or an
extreme configuration?

If your basis is the typical configuration, how would an administrator
of the extreme configuration get themselves out of the situation of
pids_max being too small without the same command line option.

If we use the extreme case, then we end up with a lot of extraneous pids,
however I don't see that as being too terrible of a situation.

Robin

  parent reply	other threads:[~2010-04-22 13:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  1:40 [Patch 1/1] init: Provide a kernel start parameter to increase pid_max Mike Travis
2010-04-21  1:52 ` [Patch 1/1] init: Provide a kernel start parameter to increase pid_max v2 Mike Travis
2010-04-21  9:23   ` Alan Cox
2010-04-21 16:59     ` Hedi Berriche
2010-04-21 17:18       ` Rik van Riel
2010-04-21 17:54         ` Mike Travis
2010-04-21 19:14         ` John Stoffel
2010-04-21 19:33           ` Hedi Berriche
2010-04-21 20:10             ` John Stoffel
2010-04-21 22:24               ` Greg KH
2010-04-21 22:49                 ` Rik van Riel
2010-04-21 23:22                   ` Greg KH
2010-04-22  9:28                     ` Alan Cox
2010-04-22 12:58                       ` Jack Steiner
2010-04-22 13:57                       ` Robin Holt [this message]
2010-04-22 14:48                       ` Linus Torvalds
2010-04-22 17:08                         ` Robin Holt
2010-04-22 18:10                           ` John Stoffel
2010-04-22 20:35                           ` Andrew Morton
2010-04-25  7:16                         ` Pavel Machek
2010-04-25 17:15                           ` Linus Torvalds
2010-04-25 17:27                             ` Linus Torvalds
2010-04-25 12:13                               ` Pavel Machek
2010-04-26 19:48                             ` [Patch 1/1] init: Provide a kernel start parameter to increase pid_max v3 Mike Travis
2010-04-26 20:46                               ` Greg KH
2010-04-27  0:43                                 ` Mike Travis
2010-04-27  0:42                               ` [Patch 1/1] init: Increase pid_max based on num_possible_cpus v4 Mike Travis
2010-04-21 17:58       ` [Patch 1/1] init: Provide a kernel start parameter to increase pid_max v2 Alan Cox
2010-04-21 19:12         ` Hedi Berriche
2010-04-21 19:51           ` Greg KH
2010-04-21 20:12             ` Hedi Berriche
2010-04-21 22:05           ` Jack Steiner

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=20100422135742.GQ4920@sgi.com \
    --to=holt@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=hedi@sgi.com \
    --cc=john@stoffel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=riel@redhat.com \
    --cc=steiner@sgi.com \
    --cc=torvalds@linux-foundation.org \
    --cc=travis@sgi.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 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.