From: Paul Jackson <pj@sgi.com>
To: Paul Menage <menage@google.com>
Cc: balbir@linux.vnet.ibm.com, xemul@openvz.org,
yamamoto@valinux.co.jp, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, containers@lists.osdl.org,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [RFC][-mm] Memory controller hierarchy support (v1)
Date: Mon, 21 Apr 2008 01:33:25 -0500 [thread overview]
Message-ID: <20080421013325.03cdd1a8.pj@sgi.com> (raw)
In-Reply-To: <6599ad830804190849u31f13191m4dcca4e471493c2b@mail.gmail.com>
Paul M wrote:
> Cpusets could make use of this too, since
> it has to traverse hierarchies sometimes.
Yeah - I suppose cpusets could use it, though
it's not critical. A fair bit of work already
went into cpusets so that it would not need to
traverse this hierarchy on any critical code path,
or while holding inconvenient locks.
So cpusets shouldn't be the driving motivation
for this, but it will likely be happy to go along
for the ride.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
--
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:[~2008-04-21 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 5:35 Balbir Singh
2008-04-19 6:56 ` YAMAMOTO Takashi
2008-04-19 8:34 ` Balbir Singh
2008-04-21 0:41 ` KAMEZAWA Hiroyuki
2008-04-19 10:47 ` Pavel Emelyanov
2008-04-20 7:43 ` Balbir Singh
2008-04-19 15:49 ` Paul Menage
2008-04-20 8:16 ` Balbir Singh
2008-04-21 6:33 ` Paul Jackson [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=20080421013325.03cdd1a8.pj@sgi.com \
--to=pj@sgi.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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