From: Andi Kleen <andi@firstfloor.org>
To: Rafael Aquini <aquini@redhat.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Stephen Wilson <wilsons@start.ca>,
Andrea Arcangeli <aarcange@redhat.com>,
Christoph Lameter <cl@linux.com>, Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/mempolicy.c: make sys_mbind & sys_set_mempolicy aware of task_struct->mems_allowed
Date: Wed, 03 Aug 2011 18:59:33 -0700 [thread overview]
Message-ID: <m2d3gm0we2.fsf@firstfloor.org> (raw)
In-Reply-To: <20110803123721.GA2892@x61.redhat.com> (Rafael Aquini's message of "Wed, 3 Aug 2011 09:37:27 -0300")
Rafael Aquini <aquini@redhat.com> writes:
> Among several other features enabled when CONFIG_CPUSETS is defined,
> task_struct is enhanced with the nodemask_t mems_allowed element that
> serves to register/report on which memory nodes the task may obtain
> memory. Also, two new lines that reflect the value registered at
> task_struct->mems_allowed are added to the '/proc/[pid]/status' file:
As Christoph said this was intentionally designed this way. Originally
there was some consideration of "relative policies", but that is not
implemented and had various issues.
They're orthogonal mechanisms.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-04 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 12:37 [PATCH] mm/mempolicy.c: make sys_mbind & sys_set_mempolicy aware of task_struct->mems_allowed Rafael Aquini
2011-08-03 14:19 ` Christoph Lameter
2011-08-04 1:59 ` Andi Kleen [this message]
2011-08-04 22:07 ` Rafael Aquini
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=m2d3gm0we2.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=cl@linux.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=wilsons@start.ca \
/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;
as well as URLs for NNTP newsgroup(s).