From: David Rientjes <rientjes@google.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Tang Chen <tangchen@cn.fujitsu.com>,
hannes@cmpxchg.org, mhocko@suse.cz, bsingharora@gmail.com,
kamezawa.hiroyu@jp.fujitsu.com, cgroups@vger.kernel.org,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, guz.fnst@cn.fujitsu.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] doc, mempolicy: Fix wrong document in numa_memory_policy.txt
Date: Fri, 11 Apr 2014 03:54:53 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1404110353440.30610@chino.kir.corp.google.com> (raw)
In-Reply-To: <5347280B.3000303@infradead.org>
On Thu, 10 Apr 2014, Randy Dunlap wrote:
> On 04/01/2014 08:53 PM, Tang Chen wrote:
> > In document numa_memory_policy.txt, the following examples for flag
> > MPOL_F_RELATIVE_NODES are incorrect.
> >
> > For example, consider a task that is attached to a cpuset with
> > mems 2-5 that sets an Interleave policy over the same set with
> > MPOL_F_RELATIVE_NODES. If the cpuset's mems change to 3-7, the
> > interleave now occurs over nodes 3,5-6. If the cpuset's mems
> > then change to 0,2-3,5, then the interleave occurs over nodes
> > 0,3,5.
> >
> > According to the comment of the patch adding flag MPOL_F_RELATIVE_NODES,
> > the nodemasks the user specifies should be considered relative to the
> > current task's mems_allowed.
> > (https://lkml.org/lkml/2008/2/29/428)
> >
> > And according to numa_memory_policy.txt, if the user's nodemask includes
> > nodes that are outside the range of the new set of allowed nodes, then
> > the remap wraps around to the beginning of the nodemask and, if not already
> > set, sets the node in the mempolicy nodemask.
> >
> > So in the example, if the user specifies 2-5, for a task whose mems_allowed
> > is 3-7, the nodemasks should be remapped the third, fourth, fifth, sixth
> > node in mems_allowed. like the following:
> >
> > mems_allowed: 3 4 5 6 7
> >
> > relative index: 0 1 2 3 4
> > 5
> >
> > So the nodemasks should be remapped to 3,5-7, but not 3,5-6.
> >
> > And for a task whose mems_allowed is 0,2-3,5, the nodemasks should be
> > remapped to 0,2-3,5, but not 0,3,5.
> >
> > mems_allowed: 0 2 3 5
> >
> > relative index: 0 1 2 3
> > 4 5
> >
> >
> > Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
>
> Wow. This was not an April fools joke, right?
>
It would have been a horrible joke if it was intended to be :)
> Have there been any acks of this? I haven't seen any responses to it.
>
Because everybody in the phonebook was cc'd on it except for the author
who wrote it.
Tang, good catch.
Acked-by: David Rientjes <rientjes@google.com>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-04-11 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 3:53 Tang Chen
2014-04-10 23:23 ` Randy Dunlap
2014-04-11 8:13 ` Tang Chen
2014-04-11 10:54 ` David Rientjes [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=alpine.DEB.2.02.1404110353440.30610@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=guz.fnst@cn.fujitsu.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=rdunlap@infradead.org \
--cc=tangchen@cn.fujitsu.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