From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: Nick Piggin <npiggin@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM Mailing List <linux-mm@kvack.org>,
Eric W Biederman <ebiederm@xmission.com>,
Linux Containers <containers@lists.osdl.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Emelianov <xemul@openvz.org>
Subject: Re: [-mm PATCH 1/9] Memory controller resource counters (v6)
Date: Wed, 12 Sep 2007 15:35:14 +0530 [thread overview]
Message-ID: <46E7B9DA.6070404@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830709101742k658234b4of59f14ef27e40d14@mail.gmail.com>
Paul Menage wrote:
> Hi Balbir/Pavel,
>
> As I mentioned to you directly at the kernel summit, I think it might
> be cleaner to integrate resource counters more closely with control
> groups. So rather than controllers such as the memory controller
> having to create their own boilerplate cf_type structures and
> read/write functions, it should be possible to just call a function
> something like
>
> control_group_add_rescounter(struct cgroup *cg, struct cgroup_subsys *ss,
> struct res_counter *res,
> const char *name)
>
> and have it handle all the userspace API. This would simplify the task
> of keeping a consistent userspace API between different controllers
> using the resource counter abstraction.
>
> Paul
>
Yes, I remember discussing it with you. I would expect res_counters
definition to be dynamic (to be able to add the guarantee, soft limit,
etc) for expansion in the future. In the future, I would also like
to do hierarchical resource groups, the hierarchy would represent
the current filesystem hierarchy.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: Nick Piggin <npiggin@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux MM Mailing List <linux-mm@kvack.org>,
Eric W Biederman <ebiederm@xmission.com>,
Linux Containers <containers@lists.osdl.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Emelianov <xemul@openvz.org>
Subject: Re: [-mm PATCH 1/9] Memory controller resource counters (v6)
Date: Wed, 12 Sep 2007 15:35:14 +0530 [thread overview]
Message-ID: <46E7B9DA.6070404@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830709101742k658234b4of59f14ef27e40d14@mail.gmail.com>
Paul Menage wrote:
> Hi Balbir/Pavel,
>
> As I mentioned to you directly at the kernel summit, I think it might
> be cleaner to integrate resource counters more closely with control
> groups. So rather than controllers such as the memory controller
> having to create their own boilerplate cf_type structures and
> read/write functions, it should be possible to just call a function
> something like
>
> control_group_add_rescounter(struct cgroup *cg, struct cgroup_subsys *ss,
> struct res_counter *res,
> const char *name)
>
> and have it handle all the userspace API. This would simplify the task
> of keeping a consistent userspace API between different controllers
> using the resource counter abstraction.
>
> Paul
>
Yes, I remember discussing it with you. I would expect res_counters
definition to be dynamic (to be able to add the guarantee, soft limit,
etc) for expansion in the future. In the future, I would also like
to do hierarchical resource groups, the hierarchy would represent
the current filesystem hierarchy.
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-09-12 10:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 8:42 [-mm PATCH 0/9] Memory controller introduction (v6) Balbir Singh
2007-08-17 8:42 ` Balbir Singh
2007-08-17 8:42 ` [-mm PATCH 1/9] Memory controller resource counters (v6) Balbir Singh
2007-08-17 8:42 ` Balbir Singh
2007-08-20 8:20 ` [Devel] " Alexey Dobriyan
2007-08-20 8:20 ` Alexey Dobriyan
2007-08-20 9:01 ` Balbir Singh
2007-08-20 9:01 ` Balbir Singh
2007-09-11 0:42 ` Paul Menage
2007-09-11 0:42 ` Paul Menage
2007-09-11 0:42 ` Paul Menage
2007-09-12 10:05 ` Balbir Singh [this message]
2007-09-12 10:05 ` Balbir Singh
2007-08-17 8:42 ` [-mm PATCH 2/9] Memory controller containers setup (v6) Balbir Singh
2007-08-17 8:42 ` Balbir Singh
2007-08-17 8:42 ` [-mm PATCH 3/9] Memory controller accounting " Balbir Singh
2007-08-17 8:42 ` Balbir Singh
2007-08-17 8:42 ` Balbir Singh
2007-08-17 8:43 ` [-mm PATCH 4/9] Memory controller memory accounting (v6) Balbir Singh
2007-08-17 8:43 ` Balbir Singh
2007-08-17 8:43 ` [-mm PATCH 5/9] Memory controller task migration (v6) Balbir Singh
2007-08-17 8:43 ` Balbir Singh
2007-08-17 8:43 ` [-mm PATCH 6/9] Memory controller add per container LRU and reclaim (v6) Balbir Singh
2007-08-17 8:43 ` Balbir Singh
2007-08-17 8:43 ` Balbir Singh
2007-08-17 8:43 ` [-mm PATCH 7/9] Memory controller OOM handling (v6) Balbir Singh
2007-08-17 8:43 ` Balbir Singh
2007-08-17 8:43 ` [-mm PATCH 8/9] Memory controller add switch to control what type of pages to limit (v6) Balbir Singh
2007-08-17 8:43 ` Balbir Singh
2007-08-17 8:43 ` Balbir Singh
2007-08-17 8:44 ` [-mm PATCH 9/9] Memory controller make page_referenced() container aware (v6) Balbir Singh
2007-08-17 8:44 ` Balbir Singh
2007-08-17 8:44 ` Balbir Singh
2007-08-17 15:49 ` [-mm PATCH 0/9] Memory controller introduction (v6) Dhaval Giani
2007-08-17 15:49 ` Dhaval Giani
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=46E7B9DA.6070404@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=npiggin@suse.de \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.