From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Dave Hansen <haveblue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [lart] /bin/ps output
Date: Sat, 16 Nov 2002 15:52:29 -0800 [thread overview]
Message-ID: <20021116235229.GA32765@tapu.f00f.org> (raw)
In-Reply-To: <1037491895.24777.26.camel@irongate.swansea.linux.org.uk>
On Sun, Nov 17, 2002 at 12:11:35AM +0000, Alan Cox wrote:
> Bill - so what happens if you trim down the aio, event and ksoftirqd
> threads to a sane size (you might also want to do something about
> the fact 2.5 still runs ksoftirq too easily). Intuitively I'd go for
> a square root of the number of processors + 1 sort of function but
> what do the benchmarks say ?
IMO having various threads per-CPU is getting silly for (say) 4+
CPUs. Even for two CPUs it means quite a good number of kernel
threads.
Does anyone really know for certain that this is necessary versus
having few per-CPU threads calling into state-machine functions?
--cw
next prev parent reply other threads:[~2002-11-16 23:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 3:36 [lart] /bin/ps output Dave Hansen
2002-10-12 3:38 ` David S. Miller
2002-10-12 3:55 ` Rik van Riel
2002-10-12 11:49 ` Alan Cox
2002-10-12 3:43 ` William Lee Irwin III
2002-10-12 3:51 ` Anton Blanchard
2002-10-12 3:59 ` William Lee Irwin III
2002-10-12 4:09 ` Anton Blanchard
2002-10-12 6:53 ` David S. Miller
2002-10-12 20:15 ` Richard Henderson
2002-10-13 6:27 ` David S. Miller
2002-10-13 6:42 ` Anton Blanchard
2002-10-13 18:25 ` Richard Henderson
2002-10-13 19:25 ` Andrew Morton
2002-10-19 12:22 ` Anton Blanchard
2002-11-16 9:24 ` William Lee Irwin III
2002-11-17 0:11 ` Alan Cox
2002-11-16 23:52 ` Chris Wedgwood [this message]
2002-11-17 0:11 ` William Lee Irwin III
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=20021116235229.GA32765@tapu.f00f.org \
--to=cw@f00f.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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.