[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1705241101090.24771@east.gentwo.org>
Date: Wed, 24 May 2017 11:03:58 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: Wei Yang <richard.weiyang@...il.com>
cc: Michal Hocko <mhocko@...nel.org>, penberg@...nel.org,
rientjes@...gle.com, akpm@...ux-foundation.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] refine and rename slub sysfs
On Wed, 24 May 2017, Wei Yang wrote:
> >
> >Who is going to use those new entries and for what purpose? Why do we
> >want to expose even more details of the slab allocator to the userspace.
> >Is the missing information something fundamental that some user space
> >cannot work without it? Seriously these are essential questions you
> >should have answer for _before_ posting the patch and mention all those
> >reasons in the changelog.
>
> It is me who wants to get more details of the slub behavior.
> AFAIK, no one else is expecting this.
I would appreciate some clearer structured statistics. These are important
for diagnostics and for debugging. Do not go overboard with this. Respin
it and provide also a cleanup of the slabinfo tool? I would appreciate it.
> Hmm, if we really don't want to export these entries, why not remove related
> code? Looks we are sure they will not be touched.
Please have a look at the slabinfo code which depends on those fields in
order to display slab information. I have patchsets here that will add
more functionality to slab and those will also add additional fields to
sysfs.
Powered by blists - more mailing lists