Re: [RFC, PATCH 0/5] Going forward with Resource Management- A cpu controller
From: Rohit Seth
Date: Tue Aug 08 2006 - 13:17:18 EST
On Tue, 2006-08-08 at 11:17 +0400, Kirill Korotaev wrote:
> >>>>>Doesnt the ability to move tasks between groups dynamically affect
> >>>>>(atleast) memory controller design (in giving up ownership etc)?
> >>>>we save object owner on the object. So if you change the container,
> >>>>objects are still correctly charged to the creator and are uncharged
> >>>>correctly on free.
> >>>Seems like the object owner should also change when the object moves
> >>>from one container to another.
> >>Consider a file which is opened in 2 processes. one of the processes
> >>wants to move to another container then. How would you decide whether
> >>to change the file owner or not?
> > If a process has sufficient rights to move a file to a new container
> > then it should be okay to assign the file to the new container.
> there is no such notion as "rights to move a file to a new container".
> The same file can be opened in processes belonging to other containers.
> And you have no any clue whether to have to change the owner or not.
I think this is where more details on a design will help. What I'm
thinking is each address_space to have a container pointer. In this
case, pages belonging to a file will charge against one single container
(irrespective of how many processes are touching those pages).
> > Though the point is, if a resource (like file) is getting migrated to a
> > new container then all the attributes (like owner, #pages in memory
> > etc.) attached to that resource (file) should also migrate to this new
> > container. Otherwise the semantics of where does the resource belong
> > becomes very difficult.
> The same for many other resources. It is a big mistake thinking that most resources
> belong to the processes and the owner process can be easily determined.
Sure that some resources it wouldn't make sense to move (or find out at
which is the real owner). And I'm not saying that we have to bind them
hard to a process either...but to a single container if they belong to a
same file (for example).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/