From: "Chris Friesen" <cfriesen@nortel•com>
To: David Miller <davem@davemloft•net>
Cc: linuxppc-dev@ozlabs•org, kevdig@hypersurf•com
Subject: Re: [PATCH] genirq: Set initial default irq affinity to just CPU0
Date: Mon, 27 Oct 2008 21:46:48 -0600 [thread overview]
Message-ID: <49068B28.6080302@nortel.com> (raw)
In-Reply-To: <20081027.122524.147654861.davem@davemloft.net>
David Miller wrote:
> From: "Chris Friesen" <cfriesen@nortel•com>
>>Are there any plans for a mechanism to allow the kernel to figure
>>out (or be told) what packets cpu-affined tasks are interested in
>>and route the interrupts appropriately?
>
> No, not at all.
> Now there are plans to allow the user to add classification rules into
> the chip for specific flows, on hardware that supports this, via ethtool.
Okay, that sounds reasonable. Good to know where you're planning on going.
> Your driver is weak and doesn't support the hardware correctly, and you
> want to put the onus on everyone else with sane hardware and drivers?
I'm not expecting any action...I was just objecting somewhat to
"Networking interrupts should lock onto a single CPU, unconditionally."
Add "for a particular flow" into that and I wouldn't have said anything.
>>It's not an ideal situation, but we're sort of stuck unless we do
>>custom driver work.
> Wouldn't want you to get your hands dirty or anything like that now,
> would we? :-)))
I'd love to. But other things take time too, so we live with it for now.
Chris
next prev parent reply other threads:[~2008-10-28 3:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 15:57 [PATCH] genirq: Set initial default irq affinity to just CPU0 Kumar Gala
2008-10-24 23:18 ` David Miller
2008-10-25 21:33 ` Benjamin Herrenschmidt
2008-10-25 22:53 ` Kevin Diggs
2008-10-26 4:05 ` David Miller
2008-10-27 17:36 ` Chris Friesen
2008-10-27 18:28 ` David Miller
2008-10-27 19:10 ` Chris Friesen
2008-10-27 19:25 ` David Miller
2008-10-28 3:46 ` Chris Friesen [this message]
2008-10-27 19:43 ` Kumar Gala
2008-10-27 19:49 ` David Miller
2008-10-27 20:46 ` Kumar Gala
2008-10-26 6:48 ` Benjamin Herrenschmidt
2008-10-26 7:16 ` David Miller
2008-10-26 8:29 ` Benjamin Herrenschmidt
2008-10-27 2:30 ` Kevin Diggs
2008-10-27 2:49 ` Benjamin Herrenschmidt
2008-10-26 4:04 ` David Miller
2008-10-26 6:33 ` Benjamin Herrenschmidt
2008-10-27 13:43 ` Kumar Gala
2008-10-27 20:27 ` Benjamin Herrenschmidt
2008-10-27 20:45 ` Kumar Gala
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=49068B28.6080302@nortel.com \
--to=cfriesen@nortel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=kevdig@hypersurf$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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