From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: David Rientjes <rientjes@google.com>
Cc: Miao Xie <miaox@cn.fujitsu.com>, Paul Menage <menage@google.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpuset: update top cpuset's mems after adding a node
Date: Tue, 11 Nov 2008 10:48:39 +0900 [thread overview]
Message-ID: <20081111104419.D5BF.E1E9C6FF@jp.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0811101222470.1219@chino.kir.corp.google.com>
> 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
Ah, OK. This seems reasonable.
Then Miao-san's patch is fine.
Acked-by: Yasunori Goto <y-goto@jp.fujitsu.com>
Thanks.
--
Yasunori Goto
prev parent reply other threads:[~2008-11-11 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 6:41 Miao Xie
2008-11-10 6:56 ` Yasunori Goto
2008-11-10 7:37 ` Miao Xie
2008-11-10 12:28 ` Miao Xie
2008-11-10 20:26 ` David Rientjes
2008-11-11 1:48 ` Yasunori Goto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081111104419.D5BF.E1E9C6FF@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=miaox@cn.fujitsu.com \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®