mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Phil Endecott <phil_wueww_endecott@chezphil.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: nice and hyperthreading on atom
Date: Sun, 07 Sep 2008 11:34:58 +0200	[thread overview]
Message-ID: <1220780098.8687.40.camel@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <a36005b50809061130t1b510b7eu3f7336ebeef4f36b@mail.gmail.com>

On Sat, 2008-09-06 at 11:30 -0700, Ulrich Drepper wrote:
> On Sat, Sep 6, 2008 at 9:42 AM, Arjan van de Ven <arjan@infradead.org> wrote:
> > As an OS one COULD decide to just not schedule the nice task at all,
> > but then, especially on atom where HT has a high efficiency, your cpu
> > is mostly idle ...
> 
> One thread being idle is even on Atom the right thing to do in some
> situations.  If you have processes which, when HT is used, experience
> high pressure on the common cache(s) then you should not schedule them
> together.  We can theoretically find out whether this is the case
> using the PMCs.  With perfmon2 hopefully on the horizon soon it might
> actually be possible to automatically make these measurements.
> 
> There is another aspect I talked to Peter about already.  We really
> want concurrent threat scheduling in some cases.  For the
> implementation of helper threads you don't want two threads to be
> scheduled independently, you want them to be scheduled on a HT pair.
> Currently this isn't possible except by pinning them to fixed threads.
>  We really want to have a new way to express this type of scheduling
> (Peter, how did you call it?)

Really helps if you make sure I'm on the CC ;-)

I think I called it something like affinity grouping - but I'm still a
bit scared of the bin-packing issues involved - those will really mess
up the already complex balancing rules.


  reply	other threads:[~2008-09-07  9:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06 15:43 Phil Endecott
2008-09-06 16:31 ` Peter Zijlstra
2008-09-06 16:42 ` Arjan van de Ven
2008-09-06 18:24   ` Phil Endecott
2008-09-06 18:30   ` Ulrich Drepper
2008-09-07  9:34     ` Peter Zijlstra [this message]
2008-09-07 13:58 ` Phil Endecott
2008-09-08  1:09   ` Bill Davidsen

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=1220780098.8687.40.camel@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=arjan@infradead.org \
    --cc=drepper@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil_wueww_endecott@chezphil.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®