All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	William Lee Irwin III <wli@holomorphy.com>,
	"Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	James Cleverdon <jamesclv@us.ibm.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	John Stultz <johnstul@us.ibm.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Saxena, Sunil" <sunil.saxena@intel.com>,
	"Van Maren, Kevin" <kevin.vanmaren@UNISYS.com>,
	Andi Kleen <ak@suse.de>, Hubert Mantel <mantel@suse.de>,
	"Kamble, Nitin A" <nitin.a.kamble@intel.com>
Subject: RE: [PATCH][2.4]  generic cluster APIC support for systems with m ore than 8 CPUs
Date: Sun, 22 Dec 2002 09:21:12 -0800	[thread overview]
Message-ID: <19370000.1040577670@titus> (raw)
In-Reply-To: <C8C38546F90ABF408A5961FC01FDBF1912E1B0@fmsmsx405.fm.intel.com>

> I actually meant interrupt distribution (rather than interrupt routing).
> AFAIK, interrupt distribution right now assumes flat logical setup and
> tries to distribute the interrupt. And is disabled in case of clustered
> APIC mode.  I was just thinking loud, about the changes interrupt
> distribution code should have for systems using clustered APIC/physical
> mode (NUMAQ and non-NUMAQ).

Oh, you mean irq_balance? I'm happy to leave that turned off on NUMA-Q
until it does something less random than it does now. Getting some sort
of affinity for interrupts over a longer period is much more interesting
than providing pretty numbers under /proc/interrupts. Giving each of
the frequently used interrupts their own local CPU to process it would
be cool, but I see no purpose in continually moving them around. If you're
concerned about fairness, that's a scheduler problem to account for and
deal with, IMHO.

The provided topology functions should be able to do node_to_cpumask
and cpu_to_node mappings once that's sorted out. Treat each node as a
seperate "system" and balance within that.

M.


  parent reply	other threads:[~2002-12-22 17:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-22  6:19 [PATCH][2.4] generic cluster APIC support for systems with m ore than 8 CPUs Pallipadi, Venkatesh
2002-12-22  6:39 ` William Lee Irwin III
2002-12-22 17:21 ` Martin J. Bligh [this message]
2002-12-22 17:23 ` Martin J. Bligh
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 18:58 Protasevich, Natalie
2003-01-08 14:53 ` Alan Cox
2002-12-26  2:18 Van Maren, Kevin
2002-12-27 23:38 ` Alan Cox
2002-12-26  1:14 Protasevich, Natalie
2002-12-27 23:39 ` Alan Cox
2002-12-23  7:29 Kamble, Nitin A
2002-12-23  7:52 ` Martin J. Bligh
2002-12-23  9:46   ` Zwane Mwaikambo
2002-12-23 15:30     ` Martin J. Bligh
     [not found] <3FAD1088D4556046AEC48D80B47B478C1AEC75@usslc-exch-4.slc.unisys. com>
2002-12-22 20:41 ` Protasevich, Natalie
2002-12-22 20:52   ` Martin J. Bligh
2002-12-22  4:00 Pallipadi, Venkatesh
2002-12-22  4:05 ` Martin J. Bligh
2002-12-20 22:57 Protasevich, Natalie
2002-12-20 23:33 ` William Lee Irwin III
2002-12-25 21:41 ` Alan Cox
     [not found] <3FAD1088D4556046AEC48D80B47B478C0101F55D@usslc-exch-4.slc.unisy s.com>
2002-12-20 15:46 ` Van Maren, Kevin
2002-12-20 16:30   ` Martin J. Bligh
2002-12-20 17:16   ` 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=19370000.1040577670@titus \
    --to=mbligh@aracnet.com \
    --cc=Natalie.Protasevich@UNISYS.com \
    --cc=ak@suse.de \
    --cc=asit.k.mallick@intel.com \
    --cc=hch@infradead.org \
    --cc=jamesclv@us.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.vanmaren@UNISYS.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mantel@suse.de \
    --cc=nitin.a.kamble@intel.com \
    --cc=sunil.saxena@intel.com \
    --cc=venkatesh.pallipadi@intel.com \
    --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.