From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: Pavel Emelianov <xemul@openvz.org>,
Hugh Dickins <hugh@veritas.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
linux-kernel@vger.kernel.org, taka@valinux.co.jp,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [-mm] Add an owner to the mm_struct (v8)
Date: Sun, 06 Apr 2008 12:01:43 +0530 [thread overview]
Message-ID: <47F86E4F.2080103@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830804051631g15363456s1952fda0bb4d395d@mail.gmail.com>
Paul Menage wrote:
> On Sat, Apr 5, 2008 at 11:59 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>> >> It's easier to set it up that way. Usually the end user gets the same SLA for
>> >> memory, CPU and other resources, so it makes sense to bind the controllers together.
>> >>
>> >
>> > True - but in that case why wouldn't they have the same SLA for
>> > virtual address space too?
>> >
>>
>> Yes, mostly. That's why I had made the virtual address space patches as a config
>> option on top of the memory controller :)
>>
>
> *If* they want to use the virtual address space controller, that is.
>
> By that argument, you should make the memory and cpu controllers the
> same controller, since in your scenario they'll usually be used
> together..
Heh, Virtual address and memory are more closely interlinked than CPU and Memory.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2008-04-06 6:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 8:05 Balbir Singh
2008-04-04 8:12 ` Paul Menage
2008-04-04 8:28 ` Balbir Singh
2008-04-04 8:50 ` Paul Menage
2008-04-04 9:25 ` Balbir Singh
2008-04-04 19:11 ` Paul Menage
2008-04-05 14:47 ` Balbir Singh
2008-04-05 17:23 ` Paul Menage
2008-04-05 17:48 ` Balbir Singh
2008-04-05 17:57 ` Paul Menage
2008-04-05 18:59 ` Balbir Singh
2008-04-05 23:29 ` Paul Menage
2008-04-06 5:38 ` Balbir Singh
2008-04-08 6:37 ` Paul Menage
2008-04-08 6:52 ` Balbir Singh
2008-04-08 6:57 ` Paul Menage
2008-04-08 7:05 ` Balbir Singh
2008-04-08 7:29 ` Paul Menage
2008-04-10 9:09 ` Balbir Singh
2008-04-05 23:31 ` Paul Menage
2008-04-06 6:31 ` Balbir Singh [this message]
2008-04-08 6:32 ` Paul Menage
2008-04-07 22:09 ` Andrew Morton
2008-04-08 2:39 ` Balbir Singh
2008-04-08 2:55 ` Andrew Morton
2008-04-09 0:42 ` KAMEZAWA Hiroyuki
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=47F86E4F.2080103@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=rientjes@google.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=taka@valinux.co.jp \
--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