Re: [PATCH] memcg: make CONFIG_MEMCG depend on CONFIG_MMU

[Michal Hocko]

[Forgot to CC Balbir - sorry - the thread starts here:
http://marc.info/?l=linux-mm&m=142549243725564&w=2]

On Wed 04-03-15 14:06:35, Johannes Weiner wrote:
> On Wed, Mar 04, 2015 at 07:07:08PM +0100, Michal Hocko wrote:
> > CONFIG_MEMCG might be currently enabled also for !MMU architectures
> > which was probably an omission because Balbir had this on the TODO
> > list section (https://lkml.org/lkml/2008/3/16/59)
> > "
> > Only when CONFIG_MMU is enabled, is the virtual address space control
> > enabled. Should we do this for nommu cases as well? My suspicion is
> > that we don't have to.
> > "
> > I do not see any traces for !MMU requests after then. The code compiles
> > with !MMU but I haven't heard about anybody using it in the real life
> > so it is not clear to me whether it works and it is usable at all
> > considering how !MMU configuration is restricted.
> > 
> > Let's make CONFIG_MEMCG depend on CONFIG_MMU to make our support
> > explicit and also to get rid of few ifdefs in the code base.
> > 
> > Acked-by: Johannes Weiner <hannes@xxxxxxxxxxx>
> > Signed-off-by: Michal Hocko <mhocko@xxxxxxx>
> 
> 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 but just considering
this wasn't working since ages for anon mappings and who knows what else
doesn't work.

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.
-- 
Michal Hocko
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/