From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, lizf@cn.fujitsu.com,
linux-kernel@vger.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [RFC][PATCH 0/5] Memory controller soft limit patches (v9)
Date: Wed, 15 Jul 2009 10:55:25 +0530 [thread overview]
Message-ID: <20090715052525.GG24034@balbir.in.ibm.com> (raw)
In-Reply-To: <20090715133324.e4683ef2.kamezawa.hiroyu@jp.fujitsu.com>
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-07-15 13:33:24]:
> On Wed, 15 Jul 2009 09:38:11 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
> > * Balbir Singh <balbir@linux.vnet.ibm.com> [2009-07-10 18:29:50]:
> >
> > >
> > > From: Balbir Singh <balbir@linux.vnet.ibm.com>
> > >
> > > New Feature: Soft limits for memory resource controller.
> > >
> > > Here is v9 of the new soft limit implementation. Soft limits is a new feature
> > > for the memory resource controller, something similar has existed in the
> > > group scheduler in the form of shares. The CPU controllers interpretation
> > > of shares is very different though.
> > >
> >
> > If there are no objections to these patches, could we pick them up for
> > testing in mmotm.
> >
>
> If any, will be fixed up in mmotm. About behavior, I don't have more things
> than I've said. (dealying kswapd is not very good.)
>
> But plz discuss with Vladislav Buzov about implementation details of [2..3/5].
> ==
> [PATCH 1/2] Resource usage threshold notification addition to res_counter (v3)
>
> It seems there are multiple functionalities you can shere with them.
>
> - hierarchical threshold check
> - callback or notify agaisnt threshold.
> etc..
>
> I'm very happy if all messy things around res_counter+hierarchy are sorted out
> before diving into melting pot. I hope both of you have nice interfaces and
> keep res_counter neat.
>
I do see scope for reuse, but I've not yet gotten to reviewing v3 of
the patches. I will, I could potentially get him to base his patches
on top of this. One of the interesting things that Paul pointed out
was of global state.
--
Balbir
--
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-15 4:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 12:59 Balbir Singh
2009-07-10 12:59 ` [RFC][PATCH 1/5] Memory controller soft limit documentation (v9) Balbir Singh
2009-07-10 13:00 ` [RFC][PATCH 2/5] Memory controller soft limit interface (v9) Balbir Singh
2009-07-10 13:00 ` [RFC][PATCH 3/5] Memory controller soft limit organize cgroups (v9) Balbir Singh
2009-07-10 13:00 ` [RFC][PATCH 4/5] Memory controller soft limit refactor reclaim flags (v9) Balbir Singh
2009-07-10 13:00 ` [RFC][PATCH 5/5] Memory controller soft limit reclaim on contention (v9) Balbir Singh
2009-07-20 15:20 ` KOSAKI Motohiro
2009-07-20 15:47 ` Balbir Singh
2009-07-15 4:08 ` [RFC][PATCH 0/5] Memory controller soft limit patches (v9) Balbir Singh
2009-07-15 4:33 ` KAMEZAWA Hiroyuki
2009-07-15 5:25 ` Balbir Singh [this message]
2009-07-15 5:28 ` KOSAKI Motohiro
2009-07-15 5:32 ` Balbir Singh
2009-07-20 15:48 ` Balbir Singh
2009-07-21 0:03 ` KAMEZAWA Hiroyuki
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=20090715052525.GG24034@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.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