From: Daniel Walker <dwalker@mvista.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: David Miller <davem@davemloft.net>,
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 09:02:09 -0700 [thread overview]
Message-ID: <1221926529.1343.140.camel@localhost.localdomain> (raw)
In-Reply-To: <20080920084512.58f7fb08@infradead.org>
On Sat, 2008-09-20 at 08:45 -0700, Arjan van de Ven wrote:
> On Sat, 20 Sep 2008 08:29:21 -0700
> >
> > > Jen's, as stated, has block layer uses for this. I intend to use
> > > this for receive side flow seperation on non-multiqueue network
> > > cards. And Steffen Klassert has a set of IPSEC parallelization
> > > changes that can very likely make use of this.
> >
> > What's the benefit that you (or Jens) sees from migrating softirqs
> > from specific cpu's to others?
>
> it means you do all the processing on the CPU that submitted the IO in
> the first place, and likely still has the various metadata pieces in
> its CPU cache (or at least you know you won't need to bounce them over)
In the case of networking and block I would think a lot of the softirq
activity is asserted from userspace.. Maybe the scheduler shouldn't be
migrating these tasks, or could take this softirq activity into
account ..
Daniel
next prev parent reply other threads:[~2008-09-20 16:02 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 [this message]
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
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=1221926529.1343.140.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=arjan@infradead.org \
--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).