public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Alexander Nyberg <alexn@telia.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1 dual xeon
Date: Wed, 28 Jan 2004 10:32:07 +0100	[thread overview]
Message-ID: <40178197.6060204@aitel.hist.no> (raw)
In-Reply-To: <1075223587.1173.5.camel@llhosts>

Alexander Nyberg wrote:

> But I can't see a reason for not dividing the different interrupt on
> different cpu's and letting them stay put. 

You want to spread the load, but that is hard to do without knowing
which interrupt sources are heavy and which are light.
Dividing them once might end up with keyboard & mouse interrupts
on one cpu and network+disk on another.  This is clearly imbalanced.

An irq balancing utility will fix this, by balancing based
on interrupt count.


> Maybe if you keep all
> interrupts on the same cpu the cache on the other ones will not have to
> be flushed often, which would be a good thing.
> 
> How would it be to maybe remove all interrupts from a cpu (except
> between cpu's) and have a few cpu's merely working with data and one "in
> control". Bad idea I guess as I haven't seen any such work.

Makes sense only if the amounts of interrupt work and other work matches
the division you make.  

Helge Hafting


      parent reply	other threads:[~2004-01-28  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25  1:36 2.6.1 dual xeon Wakko Warner
2004-01-25  1:43 ` Robert Love
2004-01-25 13:37   ` Wakko Warner
2004-01-27  7:38     ` Sander
2004-01-27 17:13       ` Alexander Nyberg
2004-01-27 17:41         ` Justin Cormack
2004-01-28  9:32         ` Helge Hafting [this message]

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=40178197.6060204@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=alexn@telia.com \
    --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