From: Herbert Poetzl <herbert@13thfloor.at>
To: Srivatsa Vaddagiri <vatsa@in.ibm.com>
Cc: menage@google.com, xemul@sw.ru, dev@sw.ru, pj@sgi.com,
sam@vilain.net, ebiederm@xmission.com, winget@google.com,
serue@us.ibm.com, akpm@linux-foundation.org,
containers@lists.osdl.org, linux-kernel@vger.kernel.org,
ckrm-tech@lists.sourceforge.net
Subject: Re: Summary of resource management discussion
Date: Wed, 14 Mar 2007 00:50:51 +0100 [thread overview]
Message-ID: <20070313235051.GA5000@MAIL.13thfloor.at> (raw)
In-Reply-To: <20070313175820.GA21825@in.ibm.com>
On Tue, Mar 13, 2007 at 11:28:20PM +0530, Srivatsa Vaddagiri wrote:
> On Tue, Mar 13, 2007 at 05:24:59PM +0100, Herbert Poetzl wrote:
> > what about identifying different resource categories and
> > handling them according to the typical usage pattern?
> >
> > like the following:
> >
> > - cpu and scheduler related accounting/limits
> > - memory related accounting/limits
> > - network related accounting/limits
> > - generic/file system related accounting/limits
> >
> > I don't worry too much about having the generic/file stuff
> > attached to the nsproxy, but the cpu/sched stuff might be
> > better off being directly reachable from the task
>
> I think we should experiment with both combinations (a direct pointer
> to cpu_limit structure from task_struct and an indirect pointer), get
> some numbers and then decide. Or do you have results already with
> respect to that?
nope, no numbers for that, but I appreciate some testing
and probably can do some testing in this regard too
(although I want to get some testing done for the resource
sharing between guests first)
> > > 3. How are cpusets related to vserver/containers?
> > >
> > > Should it be possible to, lets say, create exclusive cpusets and
> > > attach containers to different cpusets?
> >
> > that is what Linux-VServer does atm, i.e. you can put
> > an entire guest into a specific cpu set
>
> Interesting. What abt /dev/cpuset view?
host only for now
best,
Herbert
> Is that same for all containers or do you restrict that view
> to the containers cpuset only?
>
> --
> Regards,
> vatsa
> _______________________________________________
> Containers mailing list
> Containers@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/containers
next prev parent reply other threads:[~2007-03-13 23:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 12:42 Summary of resource management discussion Srivatsa Vaddagiri
2007-03-13 16:24 ` Herbert Poetzl
2007-03-13 17:58 ` Srivatsa Vaddagiri
2007-03-13 23:50 ` Herbert Poetzl [this message]
2007-03-15 11:24 ` Paul Menage
2007-03-15 17:04 ` Srivatsa Vaddagiri
2007-03-15 19:12 ` Paul Menage
2007-03-16 1:40 ` Srivatsa Vaddagiri
2007-03-16 20:03 ` Eric W. Biederman
2007-03-16 14:26 ` Herbert Poetzl
2007-03-16 14:19 ` Herbert Poetzl
2007-03-16 14:57 ` Srivatsa Vaddagiri
2007-03-16 21:23 ` Paul Jackson
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=20070313235051.GA5000@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=akpm@linux-foundation.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=containers@lists.osdl.org \
--cc=dev@sw.ru \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=pj@sgi.com \
--cc=sam@vilain.net \
--cc=serue@us.ibm.com \
--cc=vatsa@in.ibm.com \
--cc=winget@google.com \
--cc=xemul@sw.ru \
/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;
as well as URLs for NNTP newsgroup(s).