From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Dan Malek <dan@embeddedalley.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Paul Menage <menage@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Vladislav Buzov <vbuzov@embeddedalley.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Containers Mailing List
<containers@lists.linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] Memory usage limit notification addition to memcg
Date: Thu, 16 Jul 2009 22:45:30 +0530 [thread overview]
Message-ID: <20090716171530.GC3576@balbir.in.ibm.com> (raw)
In-Reply-To: <9B7C6FE2-D946-4286-9537-C4A715997B89@embeddedalley.com>
* Dan Malek <dan@embeddedalley.com> [2009-07-14 12:13:32]:
> If you look at my presentation from the last ELC, you
> will see this patch is one small step of many to improve
> resource management. This event notification discussion
> is important, but still just a tiny implementation detail in
> a bigger resource management scheme. We need to
> make the small steps to make people aware of new features,
> write applications that utilize these features, and to
> perhaps discover something even better we aren't
> even considering.
Dan, if you are suggesting that we incrementally add features, I
completely agree with you, that way the code is reviewable and
maintainable. As we add features we need to
1. Look at reuse
2. Make sure the design is sane and will not prohibit further
development.
--
Balbir
next prev parent reply other threads:[~2009-07-16 17:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 22:08 [PATCH] " Dan Malek
2009-04-13 23:08 ` Andrew Morton
2009-04-13 23:45 ` Dan Malek
2009-04-13 23:54 ` Andrew Morton
2009-04-14 0:52 ` Dan Malek
2009-04-15 0:35 ` KAMEZAWA Hiroyuki
2009-04-15 2:34 ` Dan Malek
2009-04-15 2:58 ` KAMEZAWA Hiroyuki
2009-04-15 7:32 ` Dan Malek
2009-04-15 7:33 ` KAMEZAWA Hiroyuki
2009-04-15 8:24 ` Balbir Singh
2009-04-15 17:35 ` Dan Malek
2009-04-16 3:15 ` Balbir Singh
2009-07-07 20:25 ` [PATCH 0/1] " Vladislav Buzov
2009-07-07 20:25 ` [PATCH 1/1] " Vladislav Buzov
2009-07-08 0:56 ` KAMEZAWA Hiroyuki
2009-07-09 1:43 ` Vladislav D. Buzov
2009-07-13 0:52 ` KAMEZAWA Hiroyuki
2009-07-13 21:21 ` Vladislav D. Buzov
2009-07-13 22:15 ` Paul Menage
2009-07-14 1:00 ` Vladislav D. Buzov
2009-07-14 1:03 ` KAMEZAWA Hiroyuki
2009-07-14 1:43 ` KOSAKI Motohiro
2009-07-14 19:13 ` Dan Malek
2009-07-16 17:15 ` Balbir Singh [this message]
2009-07-16 18:16 ` Dan Malek
2009-07-17 2:33 ` Balbir Singh
2009-07-15 6:02 ` Balbir Singh
2009-07-08 3:52 ` Balbir Singh
2009-07-10 18:01 ` 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 ` [PATCH 0/2] Memory usage limit notification feature (v3) Paul Menage
2009-07-14 0:31 ` 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=20090716171530.GC3576@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=dan@embeddedalley.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--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
all inboxes | Powered by JetHome®