From: Paul Menage <menage@google.com>
To: Vladislav Buzov <vbuzov@embeddedalley.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Containers Mailing List
<containers@lists.linux-foundation.org>,
Linux memory management list <linux-mm@kvack.org>,
Dan Malek <dan@embeddedalley.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH 0/2] Memory usage limit notification feature (v3)
Date: Mon, 13 Jul 2009 17:20:08 -0700 [thread overview]
Message-ID: <6599ad830907131720j4f7e1649y4866d2ddeae862c5@mail.gmail.com> (raw)
In-Reply-To: <1247530581-31416-1-git-send-email-vbuzov@embeddedalley.com>
On Mon, Jul 13, 2009 at 5:16 PM, Vladislav
Buzov<vbuzov@embeddedalley.com> wrote:
>
> The following sequence of patches introduce memory usage limit notification
> capability to the Memory Controller cgroup.
>
> This is v3 of the implementation. The major difference between previous
> version is it is based on the the Resource Counter extension to notify the
> Resource Controller when the resource usage achieves or exceeds a configurable
> threshold.
>
> TODOs:
>
> 1. Another, more generic notification mechanism supporting different events
> is preferred to use, rather than creating a dedicated file in the Memory
> Controller cgroup.
I think that defining the the more generic userspace-API portion of
this TODO should come *prior* to the new feature in this patch, even
if the kernel implementation isn't initially generic.
Paul
--
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:[~2009-07-13 23:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1239660512-25468-1-git-send-email-dan@embeddedalley.com>
[not found] ` <1246998310-16764-1-git-send-email-vbuzov@embeddedalley.com>
[not found] ` <1246998310-16764-2-git-send-email-vbuzov@embeddedalley.com>
[not found] ` <20090708095616.cdfe8c7c.kamezawa.hiroyu@jp.fujitsu.com>
2009-07-09 1:43 ` [PATCH 1/1] Memory usage limit notification addition to memcg Vladislav D. Buzov
2009-07-13 0:52 ` KAMEZAWA Hiroyuki
2009-07-13 21:21 ` Vladislav D. Buzov
2009-07-14 0:16 ` [PATCH 0/2] Memory usage limit notification feature (v3) Vladislav Buzov
2009-07-14 0:16 ` [PATCH 1/2] Resource usage threshold notification addition to res_counter (v3) Vladislav Buzov
2009-07-14 0:16 ` [PATCH 2/2] Memory usage limit notification addition to memcg (v3) Vladislav Buzov
2009-07-14 0:30 ` [PATCH 1/2] Resource usage threshold notification addition to res_counter (v3) KAMEZAWA Hiroyuki
2009-07-14 1:29 ` Vladislav D. Buzov
2009-07-14 1:45 ` KAMEZAWA Hiroyuki
2009-07-14 0:36 ` Paul Menage
2009-07-14 0:47 ` KAMEZAWA Hiroyuki
2009-07-14 0:20 ` Paul Menage [this message]
2009-07-14 0:31 ` [PATCH 0/2] Memory usage limit notification feature (v3) KOSAKI Motohiro
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=6599ad830907131720j4f7e1649y4866d2ddeae862c5@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=dan@embeddedalley.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbuzov@embeddedalley.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;
as well as URLs for NNTP newsgroup(s).