From: Arthur Kepner <akepner@sgi.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [RFC/PATCHv2] x86/irq: round-robin distribution of irqs to cpus w/in node
Date: Tue, 19 Oct 2010 16:58:42 -0700 [thread overview]
Message-ID: <20101019235842.GH2440@sgi.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010171201410.2496@localhost6.localdomain6>
On Sun, Oct 17, 2010 at 12:44:07PM +0200, Thomas Gleixner wrote:
> ....
> Looked a bit deeper into the users. Quite a bunch do
>
> pci_enable_msix();
> request_irqs();
>
> in their probe function. There is no sign of making them per cpu or
> node. mlx4 is one of them. No sign of anything related to nodes or cpus in
> the whole driver.
>
> Even if the driver does not request the irqs from the probe function,
> why does it need to do the msi/msix setup in the probe function at
> all?
>
> Wouldn't it be sufficient to do that at open() right before the
> interrupts are requested.
That's a good point.
> .....
> The fundamental flaw of arch_setup_msi_irqs() is
>
> node = dev_to_node(&dev->dev);
>
> That's the only node information we get. So we put everything on a
> single node.
>
But it's even worse than that, because we put everything on a single
cpu within the node until no vectors are left there, then move on to the
next one...
--
Arthur
prev parent reply other threads:[~2010-10-19 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 20:34 [RFC/PATCHv2] x86/irq: round-robin distribution of irqs to cpus w/in node Arthur Kepner
2010-09-27 20:46 ` Thomas Gleixner
2010-09-27 22:01 ` Arthur Kepner
2010-09-27 22:12 ` Thomas Gleixner
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 [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=20101019235842.GH2440@sgi.com \
--to=akepner@sgi.com \
--cc=ebiederm@xmission.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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