[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100520.021802.38283651.davem@davemloft.net>
Date: Thu, 20 May 2010 02:18:02 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jens.axboe@...cle.com
Cc: peterz@...radead.org, suresh.b.siddha@...el.com, mingo@...e.hu,
tglx@...utronix.de, arjan@...ux.jf.intel.com, venki@...gle.com,
svaidy@...ux.vnet.ibm.com, ego@...ibm.com,
linux-kernel@...r.kernel.org, linux@...inikbrodowski.net,
ncunningham@...a.org.au
Subject: Re: [patch 3/7] softirq: avoid softirq_work_list for SCHED_SOFTIRQ
when sent remotely
From: Jens Axboe <jens.axboe@...cle.com>
Date: Thu, 20 May 2010 10:23:09 +0200
> On Thu, May 20 2010, David Miller wrote:
>> From: Peter Zijlstra <peterz@...radead.org>
>> Date: Thu, 20 May 2010 10:12:39 +0200
>>
>> > Most odd all that, Dave, Jens, what happened to all that remote_softirq
>> > stuff?
>>
>> Nobody ended up using this remote softirq infrastructure, it can be
>> completely deleted.
>
> What parts of it? There has been reworks of parts of the code since I
> added it, the block layer only uses __smp_call_function_single() to
> trigger remote softirqs.
And that's what the networking is using for RPS/RFS too.
--
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