From: Peter Zijlstra <peterz@infradead.org>
To: Bryon Roche <kain@kain.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hackbench [pthread mode] regression with 2.6.29-rc3
Date: Mon, 02 Feb 2009 21:50:48 +0100 [thread overview]
Message-ID: <1233607848.10184.14.camel@laptop> (raw)
In-Reply-To: <gm7bmu$uo$1@ger.gmane.org>
On Mon, 2009-02-02 at 17:49 +0000, Bryon Roche wrote:
don't drop CCs
> On Mon, 02 Feb 2009 09:53:38 +0100, Peter Zijlstra wrote:
>
> > On Mon, 2009-02-02 at 09:12 +0800, Zhang, Yanmin wrote:
> >
> > I would rather go back to the old model where we iterate all threads,
> > and find a way to not make programs with too many threads for their own
> > good lock up the kernel, but instead get poor service.
>
> Now, there's an interesting question, what is the definition of too many
> threads for a program's own good? When evaluating this, please assume
> that you
> do actually have enough RAM to keep thread stacks/other userspace
> threading
> resources in-core.
In my book a program has too many threads when it outnumbers the number
of cpus available to it by an order of so.
next prev parent reply other threads:[~2009-02-02 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 7:30 Zhang, Yanmin
[not found] ` <d3f22a0902010026q1db36381j36cb1c9803d48431@mail.gmail.com>
2009-02-01 8:29 ` Lin Ming
2009-02-01 9:17 ` Peter Zijlstra
2009-02-01 9:57 ` Peter Zijlstra
2009-02-01 10:04 ` Ingo Molnar
2009-02-02 1:12 ` Zhang, Yanmin
2009-02-02 8:53 ` Peter Zijlstra
2009-02-02 17:49 ` Bryon Roche
2009-02-02 20:50 ` Peter Zijlstra [this message]
2009-02-03 11:56 ` [RFC] process wide itimer cruft Peter Zijlstra
2009-02-03 17:23 ` Oleg Nesterov
2009-02-03 17:51 ` Peter Zijlstra
2009-02-03 18:22 ` Oleg Nesterov
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=1233607848.10184.14.camel@laptop \
--to=peterz@infradead.org \
--cc=kain@kain.org \
--cc=linux-kernel@vger.kernel.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 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®