mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Balaji Rao <balajirrao@gmail.com>
To: "Paul Menage" <menage@google.com>
Cc: linux-kernel@vger.kernel.org, containers@lists.osdl.org,
	dhaval@linux.vnet.ibm.com, balbir@in.ibm.com,
	a.p.zijlstra@chello.nl, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: [RFC][-mm] [0/2] Basic stats for cgroups V2
Date: Tue, 8 Apr 2008 19:19:14 +0530	[thread overview]
Message-ID: <200804081919.14601.balajirrao@gmail.com> (raw)
In-Reply-To: <6599ad830804080036h5496e3bdv9ac2dedf0f04f9bc@mail.gmail.com>

On Tuesday 08 April 2008 01:06:17 pm Paul Menage wrote:
> 
> One of the important API choices would be whether the stats API was
> fixed in header files shared with userspace, or whether it would be
> possible for stats to be added and dynamically discovered/used by
> userspace without needing fixed header file descriptions.
> 
The second idea is much better, I feel.

> The difference would be a bit like the old sysctl API (where each
> sysctl entry had to be enumerated in a header file) versus the newer
> /proc/sys approach where numerical values aren't used and userspace
> can determine which entries are supported at runtime, and even access
> new previously-unknown entries.
> 

<snip>

> 
> Thoughts?

Overall the idea looks good to me.

We are also looking at a generic framework in cgroups that would delegate the 
job of handling statistics to the cgroup framework itself. This would avoid 
code duplication across various controllers.

-- 
regards,
Balaji Rao

  parent reply	other threads:[~2008-04-08 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 18:09 Balaji Rao
2008-04-06  6:25 ` Balbir Singh
2008-04-08  7:36 ` Paul Menage
2008-04-08 10:30   ` Balbir Singh
2008-04-08 14:53     ` Paul Menage
2008-04-08 13:49   ` Balaji Rao [this message]
2008-04-08 14:52     ` Paul Menage
2008-04-08 16:32       ` Balaji Rao

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=200804081919.14601.balajirrao@gmail.com \
    --to=balajirrao@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=balbir@in.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=mingo@elte.hu \
    /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®