linux-kernel - Re: [PATCH] cpuset: update top cpuset's mems after adding a node

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: <alpine.DEB.2.00.0811101222470.1219@chino.kir.corp.google.com>
Date:	Mon, 10 Nov 2008 12:26:50 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Miao Xie <miaox@...fujitsu.com>
cc:	Yasunori Goto <y-goto@...fujitsu.com>,
	Paul Menage <menage@...gle.com>,
	Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cpuset: update top cpuset's mems after adding a node

On Mon, 10 Nov 2008, Miao Xie wrote:

> on 2008-11-10 14:56 Yasunori Goto wrote:
> > Did you test this patch?  Was it OK?
> 
> I did it on IA64 just now. Updating top cpuset's mems is fine.
> But I forgot to update the mems_allowed of every task in top cpuset group.
> It is difficult to fix it, because I don't know whether updating a memory-bound
> task's mem_allowed is good or not.
> 

There's a fix pending in the mmotm tree that calls 
cpuset_update_task_memory_state() in the slow path of the page allocator, 
so if one of these tasks fails to allocate memory, its cached mems_allowed 
nodemask will be updated to include the new node(s).

The patch is available at 
http://userweb.kernel.org/~akpm/mmotm/broken-out/cpusets-update-mems-allowed-in-page-allocator.patch
--
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/