From: Thomas Gleixner <tglx@linutronix.de>
To: Arthur Kepner <akepner@sgi.com>
Cc: linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [RFC/PATCH] notify user-level IRQ balancer when kernel assigns IRQ affinity
Date: Thu, 9 Sep 2010 10:54:50 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1009091050370.2477@localhost6.localdomain6> (raw)
In-Reply-To: <20100903210554.GO2464@sgi.com>
On Fri, 3 Sep 2010, Arthur Kepner wrote:
It might be helpful to cc the maintainer of kernel/irq on patches
which affect that area.
>
> We've run into situations where a CPU runs out of interrupt
> vectors, because all the interrupts are getting the default
> affinity (and the interrupt balancer hasn't yet run).
>
> The following emits a netlink message whenever an interrupt
> is given a default CPU affinity. A user-level IRQ balancer
> can use those messages to decide if, and how to reassign
> affinities. This should allow us to avoid running out of
> vectors on any particular CPU (or at least make it far less
> likely).
Errm. If the irq balancer has not been run, then why should some new
irq balancer be up and running at this time. In the worst case you
need to sort that out during boot _before_ you even hit userspace.
Further this adds just redundant information as user space is already
notified about a new device being setup via udev, so what's the point
of adding another notification mechanism.
Thanks,
tglx
next prev parent reply other threads:[~2010-09-09 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 21:05 Arthur Kepner
2010-09-03 21:10 ` David Daney
2010-09-03 21:25 ` Arthur Kepner
2010-09-03 21:48 ` David Miller
2010-09-09 8:54 ` Thomas Gleixner [this message]
2010-09-09 15:55 ` Arthur Kepner
2010-09-09 16:16 ` [PATCH] MAINTAINERS: Add IRQ SUBSYSTEM Joe Perches
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.1009091050370.2477@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=akepner@sgi.com \
--cc=davem@davemloft.net \
--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
all inboxes | Powered by JetHome®