From: "Chris Friesen" <cfriesen@nortel.com>
To: David Miller <davem@davemloft.net>
Cc: 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: Mon, 22 Sep 2008 15:22:36 -0600 [thread overview]
Message-ID: <48D80C9C.2070108@nortel.com> (raw)
In-Reply-To: <20080919.234824.223177211.davem@davemloft.net>
David Miller wrote:
> Jens Axboe has written some hacks for the block layer that allow
> queueing softirq work to remote cpus. In the context of the block
> layer he used this facility to trigger the softirq block I/O
> completion on the same cpu where the I/O was submitted.
<snip>
> I intend to use this
> for receive side flow seperation on non-multiqueue network cards.
I'm not sure this belongs in this particular thread but I was
interested in how you're planning on doing this? Is there going to be a
way for userspace to specify which traffic flows they'd like to direct
to particular cpus, or will the kernel try to figure it out on the fly?
We have application guys that would like very much to be able to nail
specific apps to specific cores and have the kernel send all their
packets to those cores for processing.
Chris
next prev parent reply other threads:[~2008-09-22 21:22 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
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 [this message]
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=48D80C9C.2070108@nortel.com \
--to=cfriesen@nortel.com \
--cc=davem@davemloft.net \
--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).