[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090716171530.GC3576@balbir.in.ibm.com>
Date: Thu, 16 Jul 2009 22:45:30 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: Dan Malek <dan@...eddedalley.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Paul Menage <menage@...gle.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Vladislav Buzov <vbuzov@...eddedalley.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Containers Mailing List
<containers@...ts.linux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/1] Memory usage limit notification addition to memcg
* Dan Malek <dan@...eddedalley.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists