Messages in this thread | | | Subject | Re: [Patch 01/05]- Containers: Documentation on using containers | From | Rohit Seth <> | Date | Fri, 15 Sep 2006 09:45:25 -0700 |
| |
On Fri, 2006-09-15 at 08:15 +0200, Rolf Eike Beer wrote: > Rohit Seth wrote: > > This patch contains the Documentation for using containers. > > > +5- Remove a task from container > > + echo <pid> rmtask > > echo <pid> > rmtask? >
rmtask is an attribute defined in test_container directory. So, first you have to cd into container directory (cd /mnt/configfs/containers/test_container and then execute this command)
> Please also give a short description what containers are for. From what I read > here I can only guess it's about gettings some statistics about a group of > tasks.
Containers allow different workloads to be run on the same platform with limits defined on per container basis. This basically allows a single platform to be (soft) partitioned among different workloads (each of which could be running many tasks). The limits could be amount of memory, number of tasks among other features. These two features are already implemented in the patch set that I posted. But it is possible to add other controllers like CPU that allows only finite amount of time to the processes belonging to a container.
Currently this patch set is only tracking user memory (both file based and anonymous). The memory handler is currently deactivating pages belonging to a container that has gone over the limit. Even though this allows containers to go over board their limits but 1- once they are over the limit then they run in degraded manner and 2- if there is any memory pressure then the (extra) pages belonging to this container are the prime candidates for swapping (for example). The statistics that are shown in each container directory are the current values of each resource consumption.
Please let me know if you need any more specific information about the patch set.
-rohit
- 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/
| |