[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080614185107.GA2470@ami.dom.local>
Date: Sat, 14 Jun 2008 20:51:07 +0200
From: Jarek Poplawski <jarkao2@...il.com>
To: Oleg Nesterov <oleg@...sign.ru>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Jarek Poplawski <jarkao2@...pl>,
Max Krasnyansky <maxk@...lcomm.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] workqueues: implement flush_work()
On Sat, Jun 14, 2008 at 05:59:51PM +0400, Oleg Nesterov wrote:
> On 06/14, Jarek Poplawski wrote:
...
> > Another question is if schedule_on_each_cpu() is really such a good
> > example here: it seems these "xxx && yyy" examples could be faster,
> > but I've lost track of this earlier thread.
>
> schedule_on_each_cpu() can't use cancel_ + ->func(), the code should
> be executed on the remote CPU.
???
Actually I meant this "xxx && yyy" schedule_on_each_cpu():
http://marc.info/?l=linux-kernel&m=121329259203187&w=2
Regards,
Jarek P.
--
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