From: Rohit Seth <rohitseth@google.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Rolf Eike Beer <eike-kernel@sf-tec.de>,
Andrew Morton <akpm@osdl.org>,
devel@openvz.org, CKRM-Tech <ckrm-tech@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 01/05]- Containers: Documentation on using containers
Date: Fri, 15 Sep 2006 11:19:14 -0700 [thread overview]
Message-ID: <1158344354.12311.71.camel@galaxy.corp.google.com> (raw)
In-Reply-To: <20060915174412.GB5285@atjola.homenet>
On Fri, 2006-09-15 at 19:44 +0200, Björn Steinbrink wrote:
> On 2006.09.15 09:45:25 -0700, Rohit Seth wrote:
> > 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)
>
> The > is missing in the patch though, guess that's what Rolf wanted to
> point out ;)
>
Aha. Will fix it.
> >
> > > 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.
>
> A general description for the containers needs to go into Documentation/
> along with the usage example, so that potential users know what to do
> with it. The above seems fine, just remove the "this patch" references.
>
Okay.
Thanks,
-rohit
next prev parent reply other threads:[~2006-09-15 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 1:38 Rohit Seth
2006-09-15 6:15 ` Rolf Eike Beer
2006-09-15 10:12 ` [Devel] " Kir Kolyshkin
2006-09-15 16:46 ` Rohit Seth
2006-09-15 16:45 ` Rohit Seth
2006-09-15 17:44 ` Björn Steinbrink
2006-09-15 18:19 ` Rohit Seth [this message]
2006-09-19 15:32 ` Valdis.Kletnieks
2006-09-19 16:30 ` Rohit Seth
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=1158344354.12311.71.camel@galaxy.corp.google.com \
--to=rohitseth@google.com \
--cc=B.Steinbrink@gmx.de \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=devel@openvz.org \
--cc=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome