From: Dave Olson <olson@pathscale.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
discuss@x86-64.org
Subject: Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
Date: Thu, 13 Jul 2006 12:34:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607131232350.3583@topaz.pathscale.com> (raw)
In-Reply-To: <m1fyh5z4ys.fsf@ebiederm.dsl.xmission.com>
On Thu, 13 Jul 2006, Eric W. Biederman wrote:
| > I imagine at least some other drivers would like to know when their interrupt
| > configuration changes, also, so an interface where a driver can register
| > a callback handler seems like the right generic answer, or more simply,
| > a way for a driver to say it doesn't want it's interrupt handler
| > migrated (which we would like anyway, for performance reasons).
|
| As I recall that is "killall irqbalanced"
That's the way for the user or admin to do it. It would be good
for a driver to be able to say "I like my interrupt here, please
don't move it". It can be advisory, rather than mandatory, but
there are often cases where one driver is hurt by something that
is generally beneficial, and disabling it everywhere is a big
hammer.
It works, but it's not ideal. Different issue than you are
dealing with, but I thought it was worth bringing up, as long
as we are talking about moving interrupts.
Dave Olson
dave.olson@qlogic.com
prev parent reply other threads:[~2006-07-13 19:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 22:14 [PATCH 1/2] Add Hypertransport capability defines Eric W. Biederman
2006-07-10 22:26 ` [PATCH 2/2] Initial generic hypertransport interrupt support Eric W. Biederman
2006-07-10 22:39 ` Benjamin Herrenschmidt
2006-07-11 3:51 ` Eric W. Biederman
2006-07-11 5:20 ` Benjamin Herrenschmidt
2006-07-11 6:29 ` Eric W. Biederman
2006-07-11 7:29 ` Segher Boessenkool
2006-07-11 7:48 ` Eric W. Biederman
2006-07-11 9:15 ` Benjamin Herrenschmidt
2006-07-11 19:56 ` Eric W. Biederman
2006-07-11 22:18 ` Benjamin Herrenschmidt
2006-07-11 22:27 ` Andi Kleen
2006-07-12 3:05 ` Eric W. Biederman
2006-07-12 6:10 ` Dave Olson
2006-07-12 6:56 ` Eric W. Biederman
2006-07-13 3:56 ` Dave Olson
2006-07-13 15:13 ` Eric W. Biederman
2006-07-13 18:15 ` Dave Olson
2006-07-13 18:41 ` Eric W. Biederman
2006-07-13 19:00 ` Dave Olson
2006-07-13 19:20 ` Eric W. Biederman
2006-07-13 19:34 ` Dave Olson [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=Pine.LNX.4.64.0607131232350.3583@topaz.pathscale.com \
--to=olson@pathscale.com \
--cc=ak@suse.de \
--cc=benh@kernel.crashing.org \
--cc=discuss@x86-64.org \
--cc=ebiederm@xmission.com \
--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®