linux-kernel - Re: [PATCH wq#for-next] workqueue: Clarify that schedule_on_each

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20101020092011.62bff582.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Wed, 20 Oct 2010 09:20:11 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Mel Gorman <mel@....ul.ie>,
	lkml <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Wu Fengguang <fengguang.wu@...el.com>,
	Michal Hocko <mhocko@...e.cz>
Subject: Re: [PATCH wq#for-next] workqueue: Clarify that
 schedule_on_each_cpu is synchronous

On Tue, 19 Oct 2010 11:18:46 +0200
Tejun Heo <tj@...nel.org> wrote:

> The documentation for schedule_on_each_cpu() states that it calls a
> function on each online CPU from keventd.  This can easily be
> interpreted as an asyncronous call because the description does not
> mention that flush_work is called.  Clarify that it is synchronous.
> 
> tj: rephrased a bit
> 
> Signed-off-by: Mel Gorman <mel@....ul.ie>
> Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
> Signed-off-by: Tejun Heo <tj@...nel.org>

Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>

--
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/