From: Jack Steiner <steiner@sgi.com>
To: mingo@elte.hu, tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] x86: irq vector assignment
Date: Wed, 30 Jun 2010 10:08:29 -0500 [thread overview]
Message-ID: <20100630150829.GA14307@sgi.com> (raw)
In-Reply-To: <20100624193413.GA20457@sgi.com>
Try to assign irq vectors to cpus on the correct node & fall back to global
assignment only if node-local fails. This reduces the chances of
using all of the interrupt vectors of a single cpu.
Signed-off-by: Jack Steiner <steiner@sgi.com>
---
V2 - Fix error for builds without CONFIG_NUMA.
On Thu, Jun 24, 2010 at 01:45:40PM -0700, Yinghai Lu wrote:
> how about update apic::target_cpus() to take node?
I may be overlooking something but I don't see the benefit of passing node to target_cpus().
It looks like only 1 place that calls target_cpus() has a valid "node". The other places would
pass -1. In addition, I'm not sure how some of the other subarches (ex., es7000_32) would
use the node number. Many would just ignore it.
---
arch/x86/kernel/apic/io_apic.c | 5 +++++
1 file changed, 5 insertions(+)
Index: linux/arch/x86/kernel/apic/io_apic.c
===================================================================
--- linux.orig/arch/x86/kernel/apic/io_apic.c 2010-06-25 08:11:07.186867196 -0500
+++ linux/arch/x86/kernel/apic/io_apic.c 2010-06-25 08:41:51.790274150 -0500
@@ -3265,6 +3265,11 @@ unsigned int create_irq_nr(unsigned int
desc_new = move_irq_desc(desc_new, node);
cfg_new = desc_new->chip_data;
+#ifdef CONFIG_NUMA
+ if (node >= 0 && __assign_irq_vector(new, cfg_new, node_to_cpumask_map[node]) == 0)
+ irq = new;
+ else
+#endif
if (__assign_irq_vector(new, cfg_new, apic->target_cpus()) == 0)
irq = new;
break;
prev parent reply other threads:[~2010-06-30 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 19:34 [PATCH] - irq vector assignment Jack Steiner
2010-06-24 20:45 ` Yinghai Lu
2010-06-30 15:08 ` Jack Steiner [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=20100630150829.GA14307@sgi.com \
--to=steiner@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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