Messages in this thread | | | Date | Thu, 21 Sep 2006 10:33:02 +0900 | From | KAMEZAWA Hiroyuki <> | Subject | Re: [Lhms-devel] [patch00/05]: Containers(V2)- Introduction |
| |
Self-response..
On Thu, 21 Sep 2006 09:51:00 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Wed, 20 Sep 2006 16:31:22 -0700 (PDT) > Christoph Lameter <clameter@sgi.com> wrote: > > > On Wed, 20 Sep 2006, Rohit Seth wrote: > > > > > Absolutely. Since these containers are not (hard) partitioning the > > > memory in any way so it is easy to change the limits (effectively > > > reducing and increasing the memory limits for tasks belonging to > > > containers). As you said, memory hot-un-plug is important and it is > > > non-trivial amount of work. > > > > Maybe the hotplug guys want to contribute to the discussion? > > > Ah, I'm reading threads with interest.
I wonder it may not good to use pgdat for resource controlling.
For example
In following scenario, == (1). add <pid> > /mnt/configfs/containers/my_container/add_task (2). <pid> does some work. (3). echo <pid> > /mnt/configfs/containers/my_container/rm_task (4). echo <pid> > /mnt/configfs/containers/my_container2/add_task == (if fake-pgdat/memory-hotplug is used) The pages used by <pid> in (2) will be accounted in 'my_container' after (3). Is this user's wrong use of system ?
-Kame
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |