linux-kernel - Re: [PATCH] mm: fix vmstat_update to keep scheduling itself on all cores

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] [day] [month] [year] [list]

Message-ID: <CAOtvUMcPEbG0_CTazCgf0Tb4kinzP+nmhjWQL=Juok_Bxc-r5A@mail.gmail.com>
Date:	Wed, 14 Mar 2012 16:51:15 +0200
From:	Gilad Ben-Yossef <gilad@...yossef.com>
To:	Christoph Lameter <cl@...ux.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Mel Gorman <mel@....ul.ie>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Andi Kleen <ak@...ux.intel.com>, Linux-MM <linux-mm@...ck.org>
Subject: Re: [PATCH] mm: fix vmstat_update to keep scheduling itself on all cores

On Wed, Mar 14, 2012 at 4:09 PM, Christoph Lameter <cl@...ux.com> wrote:
> On Wed, 14 Mar 2012, Gilad Ben-Yossef wrote:
>
>> We set up per-cpu work structures for vmstat and schedule them on
>> each cpu when they go online only to re-schedule them on the general
>> work queue when they first run.
>
> schedule_delayed_work queues on the current cpu unless the
> WQ_UNBOUND flag is set. Which is not set for vmstat_work.

I've missed that. My bad. Sorry for the noise.

Gilad



-- 
Gilad Ben-Yossef
Chief Coffee Drinker
gilad@...yossef.com
Israel Cell: +972-52-8260388
US Cell: +1-973-8260388
http://benyossef.com

"If you take a class in large-scale robotics, can you end up in a
situation where the homework eats your dog?"
 -- Jean-Baptiste Queru
--
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/