From: Johannes Weiner <hannes@cmpxchg.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.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: Wed, 4 Mar 2015 16:13:01 -0500 [thread overview]
Message-ID: <20150304211301.GA22626@phnom.home.cmpxchg.org> (raw)
In-Reply-To: <20150304192836.GA952@dhcp22.suse.cz>
On Wed, Mar 04, 2015 at 08:28:36PM +0100, Michal Hocko wrote:
> > Sorry about the misunderstanding, I actually acked Chen's patch. As I
> > said, there is nothing inherent in memcg that would prevent using it
> > on NOMMU systems except for this charges-follow-tasks feature, so I'd
> > rather fix the compiler warning than adding this dependency.
>
> Does it really make sense to do this minor tweaks when the configuration
> is barely usable and we are not aware of anybody actually using it in
> the real life?
>
> Sure there is nothing inherently depending on MMU
How is this even controversial? We are not adding dependencies just
because we're not sure how we feel about the opposite. We declare a
dependency when we know it truly exists.
> but just considering
> this wasn't working since ages for anon mappings and who knows what else
> doesn't work.
NOMMU people know that too, they don't expect to have significant test
coverage. If they run into issues, they can still add the dependency.
This is much better than them wanting to use a feature, running into
the dependency declaration, going through all the code, scratching
their heads about why this code would have that dependency, finally
writing us an email, and then us going "ah yeah, there is nothing
INHERENTLY depending on MMU, we just weren't sure about it."
I don't even care about NOMMU, this is just wrong on principle. And
obviously so. NAK to your patch from me.
> The point is, once somebody really needs this configuration we should go
> over all the missing parts and implement them but this half baked state
> with random fixes to shut the compiler up is really suboptimal IMO.
Disagreed, for the above-mentioned reasons. Chen's patch is obvious
and self-contained and doesn't at all indicate an endless stream of
future patches in that direction. It also improves code organization.
--
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:[~2015-03-04 21:13 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 [this message]
2015-03-04 21:21 ` Andrew Morton
2015-03-05 12:56 ` Michal Hocko
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=20150304211301.GA22626@phnom.home.cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=762976180@qq.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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