From: David Miller <davem@davemloft.net>
To: dwalker@mvista.com
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, jens.axboe@oracle.com,
steffen.klassert@secunet.com
Subject: Re: [PATCH 0/2]: Remote softirq invocation infrastructure.
Date: Sat, 20 Sep 2008 12:59:49 -0700 (PDT) [thread overview]
Message-ID: <20080920.125949.193703969.davem@davemloft.net> (raw)
In-Reply-To: <1221932404.1343.196.camel@localhost.localdomain>
From: Daniel Walker <dwalker@mvista.com>
Date: Sat, 20 Sep 2008 10:40:04 -0700
> Dave didn't supply the users of his code, or what kind of improvement
> was seen, or the case in which it would be needed. I think Dave knowns
> his subsystem, but the code on the surface looks like an end run around
> some other problem area..
I posted an example use case on netdev a few days ago, and
the block layer example is in Jen's block layer tree.
It's for networking cards that don't do flow seperation on
receive using multiple RX queues and MSI-X interrupts. It's
also for things like IPSEC where the per-packet cpu usage
is so huge (to do the crypto) that it makes sense to even
split up the work to multiple cpus within the same flow.
next prev parent reply other threads:[~2008-09-20 19:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 6:48 [PATCH 0/2]: Remote softirq invocation infrastructure David Miller
2008-09-20 15:29 ` Daniel Walker
2008-09-20 15:45 ` Arjan van de Ven
2008-09-20 16:02 ` Daniel Walker
2008-09-20 16:19 ` Arjan van de Ven
2008-09-20 17:40 ` Daniel Walker
2008-09-20 18:09 ` Arjan van de Ven
2008-09-20 18:52 ` Daniel Walker
2008-09-20 20:04 ` David Miller
2008-09-20 19:59 ` David Miller [this message]
2008-09-21 6:05 ` Herbert Xu
2008-09-21 6:57 ` David Miller
2008-09-22 10:36 ` Ilpo Järvinen
2008-09-24 4:54 ` Herbert Xu
2008-09-21 9:13 ` James Courtier-Dutton
2008-09-21 9:17 ` David Miller
2008-09-21 9:46 ` Steffen Klassert
2008-09-22 8:23 ` Herbert Xu
2008-09-22 13:54 ` Steffen Klassert
2008-09-20 20:00 ` David Miller
2008-09-22 21:22 ` Chris Friesen
2008-09-22 22:12 ` David Miller
2008-09-23 17:03 ` Chris Friesen
2008-09-23 21:10 ` Tom Herbert
2008-09-23 21:51 ` David Miller
2008-09-24 7:42 ` David Miller
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=20080920.125949.193703969.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arjan@infradead.org \
--cc=dwalker@mvista.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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).