From: Kumar Gala <galak@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: kevdig@hypersurf.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] genirq: Set initial default irq affinity to just CPU0
Date: Mon, 27 Oct 2008 15:46:49 -0500 [thread overview]
Message-ID: <6F732DEE-4F04-4A9C-A607-56F47B1F96C0@kernel.crashing.org> (raw)
In-Reply-To: <20081027.124922.116478297.davem@davemloft.net>
On Oct 27, 2008, at 2:49 PM, David Miller wrote:
> From: Kumar Gala <galak@kernel.crashing.org>
> Date: Mon, 27 Oct 2008 14:43:29 -0500
>
>> I haven't been following the netdev patches, but what about HW that
>> does flow separation w/o multiple interrupts?
>>
>> We (Freescale) are working on such a device:
>>
>> http://www.freescale.com/webapp/sps/site/prod_summary.jsp?fastpreview=1&code=P4080
>
> It could probably tie into the software based flow seperation support.
Will have to look at the code.. we might be able to fit in the HW irq
scheme. We effective have a way of getting a per cpu interrupt for
the flow.
- k
next prev parent reply other threads:[~2008-10-27 20: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
2008-10-27 19:43 ` Kumar Gala
2008-10-27 19:49 ` David Miller
2008-10-27 20:46 ` Kumar Gala [this message]
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=6F732DEE-4F04-4A9C-A607-56F47B1F96C0@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=kevdig@hypersurf.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).