From: Michal Hocko <mhocko@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Chen Gang <762976180@qq.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Balbir Singh <bsingharora@gmail.com>
Subject: Re: [PATCH] memcg: make CONFIG_MEMCG depend on CONFIG_MMU
Date: Thu, 5 Mar 2015 13:56:41 +0100 [thread overview]
Message-ID: <20150305125641.GB19347@dhcp22.suse.cz> (raw)
In-Reply-To: <20150304132126.90dad77e36b21016b5a411a4@linux-foundation.org>
On Wed 04-03-15 13:21:26, Andrew Morton wrote:
> On Wed, 4 Mar 2015 16:13:01 -0500 Johannes Weiner <hannes@cmpxchg.org> wrote:
>
> > I don't even care about NOMMU, this is just wrong on principle.
>
> Agree. And I do care about nommu ;)
>
> If some nommu person wants to start using memcg and manages to get it
> doing something useful then good for them - we end up with a better
> kernel. We shouldn't go and rule this out without having even tried it.
Fair enough, but shouldn't we be explicit (and honest) that the
configuration is currently broken and hardly usable?
Would it make sense to make MEMCG depend on BROKEN for !MMU? If somebody
really has an usecase then dependency on BROKEN would suggest there is a
work to be done before it is enabled for his/her configuration. I would
expect such a user would send us an email when noticing this and submit
a bug report so that we can help making it work.
---
prev parent reply other threads:[~2015-03-05 12:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 18:07 Michal Hocko
2015-03-04 19:06 ` Johannes Weiner
2015-03-04 19:28 ` Michal Hocko
2015-03-04 21:07 ` David Rientjes
2015-03-04 21:13 ` Johannes Weiner
2015-03-04 21:21 ` Andrew Morton
2015-03-05 12:56 ` Michal Hocko [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=20150305125641.GB19347@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=762976180@qq.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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