From: Rik van Riel <riel@redhat.com>
To: Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: fedora-devel-list@redhat.com, opensuse-packaging@opensuse.org,
lkml <linux-kernel@vger.kernel.org>,
containers@lists.linux-foundation.org,
Balbir Singh <balbir@in.ibm.com>,
menage@google.com, Peter Zijlstra <a.p.zijlstra@chello.nl>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
veillard@redhat.com
Subject: Re: [RFC] libcg: design and plans
Date: Thu, 20 Mar 2008 18:04:55 -0400 [thread overview]
Message-ID: <20080320180455.7c179008@cuia.boston.redhat.com> (raw)
In-Reply-To: <20080304152341.GB5659@linux.vnet.ibm.com>
On Tue, 4 Mar 2008 20:53:41 +0530
Dhaval Giani <dhaval@linux.vnet.ibm.com> wrote:
> Hi,
>
> We have been working on a library for control groups which would provide
> simple APIs for programmers to utilize from userspace and make use of
> control groups.
Since somebody (*cough*openvz*cough*) will no doubt add security and
network separation to the control groups at some point in the future,
why not build on libvirt?
That way admins can also use the same tools for monitoring and managing
resource groups that they use for virtual machines.
http://libvirt.org/
--
All Rights Reversed
prev parent reply other threads:[~2008-03-20 22:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 15:23 Dhaval Giani
2008-03-04 17:15 ` Xpl++
2008-03-05 4:48 ` Balbir Singh
2008-03-05 5:26 ` Dhaval Giani
2008-03-05 11:56 ` Xpl++
2008-03-05 15:53 ` Dhaval Giani
2008-03-05 19:36 ` Xpl++
2008-03-04 18:05 ` Dave Hansen
2008-03-05 6:15 ` Paul Menage
2008-03-05 7:17 ` [Devel] " Denis V. Lunev
2008-03-05 11:48 ` Balbir Singh
2008-03-05 10:33 ` Dhaval Giani
2008-03-05 10:41 ` Paul Menage
2008-03-05 11:07 ` Dhaval Giani
2008-03-05 11:51 ` Paul Menage
2008-03-05 14:24 ` Balbir Singh
2008-03-05 18:55 ` Paul Menage
2008-03-20 22:04 ` Rik van Riel [this message]
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=20080320180455.7c179008@cuia.boston.redhat.com \
--to=riel@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=balbir@in.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=fedora-devel-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=opensuse-packaging@opensuse.org \
--cc=skumar@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=veillard@redhat.com \
/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
all inboxes | Powered by JetHome®