public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andi Kleen <ak@muc.de>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	linux-kernel@vger.kernel.org
Subject: Re: CONFIG_IRQBALANCE for AMD64?
Date: Sat, 29 May 2004 20:10:39 +1000	[thread overview]
Message-ID: <40B8619F.8020108@yahoo.com.au> (raw)
In-Reply-To: <20040529100600.GA75246@colin2.muc.de>

Andi Kleen wrote:
>>We're actually doing the converse of this in the sched-domain
>>scheduler. Processes have a tendancy to follow the interrupts
>>(ie. try to get onto the same CPU as them).
> 
> 
> Hmm? I don't see any code in sched-domain that would care about
> interrupts. What I'm missing?
> 

Well no, what I should have said is wakeups. We do the same
for all wakeups, so there is nothing interrupt specific you
are right.

  reply	other threads:[~2004-05-29 10:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 22:05 CONFIG_IRQBALANCE for AMD64? Nakajima, Jun
2004-05-28 22:54 ` Andi Kleen
2004-05-29  1:27   ` Nick Piggin
2004-05-29 10:06     ` Andi Kleen
2004-05-29 10:10       ` Nick Piggin [this message]
2004-05-29 11:18         ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-05-28 23:37 Nakajima, Jun
     [not found] <20Uhn-7bP-11@gated-at.bofh.it>
     [not found] ` <20UqZ-7i7-5@gated-at.bofh.it>
2004-05-28 21:45   ` Andi Kleen
2004-05-28 18:20 Nakajima, Jun
2004-05-28 18:33 ` Martin J. Bligh
2004-05-28 18:44   ` Arjan van de Ven
2004-05-28 18:57     ` Martin J. Bligh
2004-05-28 19:01       ` Arjan van de Ven
2004-05-29  8:38     ` michael
2004-05-29  8:41     ` michael
2004-05-29  8:45       ` Arjan van de Ven
2004-05-28 17:09 Nakajima, Jun
2004-05-28 17:40 ` Jeff Garzik
2004-05-28 17:45   ` Arjan van de Ven
2004-05-28 17:46   ` Martin J. Bligh
2004-05-28 17:57     ` Arjan van de Ven
2004-05-28 19:51       ` Nivedita Singhvi
2004-05-28 19:58         ` Jeff Garzik
2004-05-28 20:14           ` Nivedita Singhvi
2004-05-28 21:45             ` Jeff Garzik
2004-05-28 20:03         ` Arjan van de Ven
2004-05-27  3:48 Thomas Zehetbauer
2004-05-27  5:13 ` Jeff Garzik
2004-05-27 16:36   ` Thomas Zehetbauer
2004-05-27 16:50     ` Arjan van de Ven
2004-05-27 21:37       ` Chris Wedgwood
2004-05-27 17:03     ` Anton Blanchard
2004-05-27 22:36       ` Thomas Zehetbauer
2004-05-28  5:57         ` Arjan van de Ven

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=40B8619F.8020108@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=ak@muc.de \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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