From: "John Stoffel" <john@stoffel.org>
To: Hedi Berriche <hedi@sgi.com>
Cc: John Stoffel <john@stoffel.org>, Rik van Riel <riel@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Mike Travis <travis@sgi.com>,
Ingo Molnar <mingo@elte.hu>, Greg Kroah-Hartman <gregkh@suse.de>,
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: Wed, 21 Apr 2010 16:10:08 -0400 [thread overview]
Message-ID: <19407.23456.469074.256306@stoffel.org> (raw)
In-Reply-To: <20100421193350.GU16427@zorg.emea.sgi.com>
>>>>> "Hedi" == Hedi Berriche <hedi@sgi.com> writes:
Hedi> On Wed, Apr 21, 2010 at 20:15 John Stoffel wrote:
Hedi> | >>>>> "Rik" == Rik van Riel <riel@redhat.com> writes:
Hedi> |
Hedi> | Rik> That is 15 kernel threads per CPU.
Hedi> |
Hedi> | Rik> Reducing the number of kernel threads sounds like a
Hedi> | Rik> useful thing to do.
Hedi> |
Hedi> | Isn't that already a project?
Hedi> Yes, thanks to Alan's probing I looked it up
Hedi> http://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git
Hedi> but we're definitely talking long term solution vs. something
Hedi> that can ease pain now.
It seems to me that running Linux on such a large machine is such a
specialized niche, the putting in your change to the regular kernel
isn't a near term need either. And from the sounds of it, Tejun's
work has better long term potential.
But hey, I'm generally clueless, so take what I say with a grain of
salt. :]
John
next prev parent reply other threads:[~2010-04-21 20:10 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 [this message]
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
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=19407.23456.469074.256306@stoffel.org \
--to=john@stoffel.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=hedi@sgi.com \
--cc=holt@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome