From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH -mm v9 0/8] idle memory tracking Date: Mon, 27 Jul 2015 12:25:27 -0700 Message-ID: <20150727122527.c6f7786177e9b5096e623d18@linux-foundation.org> References: <20150721163402.43ad2527d9b8caa476a1c9e1@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-doc-owner@vger.kernel.org To: Kees Cook Cc: Vladimir Davydov , Andres Lagar-Cavilla , Minchan Kim , Raghavendra K T , Johannes Weiner , Michal Hocko , Greg Thelen , Michel Lespinasse , David Rientjes , Pavel Emelyanov , Cyrill Gorcunov , Jonathan Corbet , Linux API , "linux-doc@vger.kernel.org" , Linux-MM , Cgroups , LKML List-Id: linux-api@vger.kernel.org On Mon, 27 Jul 2015 12:18:57 -0700 Kees Cook wrote: > > Why were these put in /proc anyway? Rather than under /sys/fs/cgroup > > somewhere? Presumably because /proc/kpageidle is useful in non-memcg > > setups. > > Do we need a /proc/vm/ for holding these kinds of things? We're > collecting a lot there. Or invent some way for this to be sensible in > /sys? /proc is the traditional place for such things (/proc/kpagecount, /proc/kpageflags, /proc/pagetypeinfo). But that was probably a mistake. /proc/sys/vm is rather a dumping ground of random tunables and statuses, but yes, I do think that moving the kpageidle stuff into there would be better.