[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080920084512.58f7fb08@infradead.org>
Date: Sat, 20 Sep 2008 08:45:12 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Daniel Walker <dwalker@...sta.com>
Cc: David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, jens.axboe@...cle.com,
steffen.klassert@...unet.com
Subject: Re: [PATCH 0/2]: Remote softirq invocation infrastructure.
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)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists