From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Steve Magnani <steve@digidescorp.com>
Cc: balbir@linux.vnet.ibm.com, linux-mm@kvack.org,
dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] nommu: add anonymous page memcg accounting
Date: Thu, 21 Oct 2010 11:42:40 +0900 [thread overview]
Message-ID: <20101021114240.8d27d39f.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <WC20101021023516.32042E@digidescorp.com>
On Wed, 20 Oct 2010 21:35:16 -0500
"Steve Magnani" <steve@digidescorp.com> wrote:
> On Thu, 2010-10-21 at 09:08 +0900, KAMEZAWA Hiroyuki wrote:
> > I myself can't maintain NOMMU kernel. So, please test every -rc1 when
> > this patch merged. OK ?
>
> It's reasonable to ask that features be tested every so often, and since the memory cgroup code seems to be
> changing relatively frequently it probably needs exercising more often. I can't commit to this, though - I
> don't know how much longer I'll be working with NOMMU kernels, and they are notoriously fragile. Any memory
> access bug that would cause an oops (or SEGV) in a "normal" kernel can cause subtle and almost impossible to
> debug behavior on a NOMMU system. For this reason I always try to work with "stable" kernels (recent threads
> debating the term notwithstanding)...so it would be a pretty far jump to a -rc1 kernel.
>
> Is this a showstopper (in which case David's patch to make the CGROUP_MEM_RES_CTLR Kconfig option depend on MMU
> should be implemented), or should I post V3 of the patch that has Balbir's suggested change?
>
I asked just because I'm curious and maintainance is always a concern.
But it's not showstopper.
BTW, my request is updating Documentaion as:
1. Please clarify "When reaching limit, OOM-Kill is inoved."
2. Add TODO List.
For example)For NOMMU guys, you don't need page_cgroup->lru because no page reclaim happens.
I think you can delete page_cgroup->lru and save much memmory.
I'll ack if v3 seems O.K. But I'm sorry it's in merge-window and people will be busy
for a while. please be patient.
Thanks,
-Kame
--
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>
prev parent reply other threads:[~2010-10-21 2:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 12:34 Steven J. Magnani
2010-10-19 15:48 ` Balbir Singh
2010-10-19 18:24 ` Steven J. Magnani
2010-10-20 0:17 ` KAMEZAWA Hiroyuki
2010-10-20 12:49 ` Steven J. Magnani
2010-10-21 0:08 ` KAMEZAWA Hiroyuki
2010-10-21 2:35 ` Steve Magnani
2010-10-21 2:42 ` KAMEZAWA Hiroyuki [this message]
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=20101021114240.8d27d39f.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=steve@digidescorp.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