From: Thomas Gleixner <tglx@linutronix.de>
To: Arthur Kepner <akepner@sgi.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [RFC/PATCHv2] x86/irq: round-robin distribution of irqs to cpus w/in node
Date: Tue, 28 Sep 2010 00:12:55 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1009280003300.2416@localhost6.localdomain6> (raw)
In-Reply-To: <20100927220113.GD30050@sgi.com>
On Mon, 27 Sep 2010, Arthur Kepner wrote:
> On Mon, Sep 27, 2010 at 10:46:02PM +0200, Thomas Gleixner wrote:
> > ...
> > Sigh. Why is this a x86 specific problem ?
> >
>
> It's obviously not. But we're particularly seeing it on x86
> systems, so an x86-specific fix would address our problem.
Even more sigh.
> > If we setup an irq on a node then we should set the affinity to the
> > target node in general.
>
> OK.
>
> > .... The round robin inside the node is really not
> > a problem unless you hit:
> >
> > nr_irqs_per_node * nr_cpus_per_node > max_vectors_per_cpu
> >
>
> No, I don't think that's true.
>
> The problem we're seeing is that one driver asks for a large
> number of interrupts (on no CPU in particular). And because of the
It does it for a node, dammit. Otherwise your patch would be
absolutely useless.
> > > + if ((node != -1) && alloc_cpumask_var(&tmp_mask, GFP_ATOMIC)) {
> way that the vectors are initially assigned to CPUs (in
> __assign_irq_vector()), a particular CPU can have all its vectors
> consumed.
Stop selling me crap already.
Thanks,
tglx
next prev parent reply other threads:[~2010-09-27 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 20:34 Arthur Kepner
2010-09-27 20:46 ` Thomas Gleixner
2010-09-27 22:01 ` Arthur Kepner
2010-09-27 22:12 ` Thomas Gleixner [this message]
2010-09-28 0:17 ` Eric W. Biederman
2010-09-28 8:08 ` Thomas Gleixner
2010-09-28 10:59 ` Eric W. Biederman
2010-09-29 17:19 ` Arthur Kepner
2010-09-29 18:05 ` Thomas Gleixner
2010-10-17 10:44 ` Thomas Gleixner
2010-10-19 23:58 ` Arthur Kepner
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=alpine.LFD.2.00.1009280003300.2416@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=akepner@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®