From: Mark Hounschell <markh@compro.net>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IRQ splitting
Date: Thu, 05 Apr 2007 09:11:09 -0400 [thread overview]
Message-ID: <4614F56D.5020704@compro.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0704051412160.31796@twin.jikos.cz>
Jiri Kosina wrote:
> On Thu, 5 Apr 2007, Jan Engelhardt wrote:
>
>> My question is whether it is possible that eth0's interrupts go to CPU0
>
> Documentation/IRQ-affinity.txt
>
There is nothing in there tells ya how to get them off the same IRQ.
That has to be done first usually be moving one of them to another
slot/bus. Then Documentation/IRQ-affinity.txt can be referenced.
Somehow I think Jan already knew that and really wants to know
how to keep them from sharing the same irq without having to
change slot assignments. I know I would.
Mark
next prev parent reply other threads:[~2007-04-05 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 10:40 IRQ splitting Jan Engelhardt
2007-04-05 12:13 ` Jiri Kosina
2007-04-05 13:11 ` Mark Hounschell [this message]
2007-04-05 14:14 ` Lennart Sorensen
[not found] <fa.21iotKLTgoLpkKhrbSxrjy5v7hM@ifi.uio.no>
2007-04-05 14:34 ` Robert Hancock
2007-04-05 19:23 ` Stephen Hemminger
2007-04-05 20:37 ` Jan Engelhardt
2007-04-05 19:45 ` Stephen Hemminger
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=4614F56D.5020704@compro.net \
--to=markh@compro.net \
--cc=jengelh@linux01.gwdg.de \
--cc=jikos@jikos.cz \
--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