Linux Container Development
 help / color / mirror / Atom feed
From: Dhaval Giani <dhaval-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	Balaji Rao <balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [Libcg-devel] Control groups and Resource Management notes (part I)
Date: Wed, 6 Aug 2008 23:08:49 +0530	[thread overview]
Message-ID: <20080806173849.GE14984@linux.vnet.ibm.com> (raw)
In-Reply-To: <489315B2.2080506-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>

On Fri, Aug 01, 2008 at 07:24:58PM +0530, Balbir Singh wrote:

> 4. Binary statistics - The question about binary statistics was raised. Since
> control groups don't enforce any particular kind of API, is there a way to
> generically handle control files and their parameters in the library? Paul
> suggested his binary API approach, where every control group and it's API is
> documented in an api file. Eric suggested using an ASCII interface (since that
> is very generic) and using one file per API. Balbir mentioned that this will
> lead to too many dentries and issues related to having extensive number of dentries.

So where are we heading with respect to this issue? Was any consensus
reached? I plan to look at enabling statistics in libcgroup soon. Also I
believe Balaji is also looking at cgroupstats.

Thanks,
-- 
regards,
Dhaval

      parent reply	other threads:[~2008-08-06 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 13:54 Control groups and Resource Management notes (part I) Balbir Singh
2008-08-02  1:10 ` Control groups and Resource Management notes (part II) Balbir Singh
2008-08-05  7:45   ` KOSAKI Motohiro
     [not found]     ` <20080805160709.A88B.KOSAKI.MOTOHIRO-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-08-05 13:30       ` [Libcg-devel] " Vivek Goyal
     [not found]         ` <20080805133007.GC15193-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-08-06  1:05           ` KAMEZAWA Hiroyuki
2008-08-06 13:00             ` Vivek Goyal
     [not found] ` <489315B2.2080506-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-08-05  7:06   ` Control groups and Resource Management notes (part I) KOSAKI Motohiro
2008-08-06 17:38   ` Dhaval Giani [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=20080806173849.GE14984@linux.vnet.ibm.com \
    --to=dhaval-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=balajirrao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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