[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 19 Sep 2011 13:59:19 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Pekka Enberg <penberg@...helsinki.fi>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Vasiliy Kulikov <segoon@...nwall.com>,
Andrew Morton <akpm@...ux-foundation.org>,
kernel-hardening@...ts.openwall.com, Kees Cook <kees@...ntu.com>,
Cyrill Gorcunov <gorcunov@...il.com>,
Al Viro <viro@...iv.linux.org.uk>,
Christoph Lameter <cl@...ux-foundation.org>,
Matt Mackall <mpm@...enic.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Dan Rosenberg <drosenberg@...curity.com>,
Theodore Tso <tytso@....edu>, Alan Cox <alan@...ux.intel.com>,
Jesper Juhl <jj@...osbits.net>
Subject: Re: Re: [RFC PATCH 2/2] mm: restrict access to
/proc/slabinfo
On Mon, 19 Sep 2011, Pekka Enberg wrote:
> Well, sure. I was actually planning to rip out SLUB merging completely
> because it makes /proc/slabinfo so useless but never got around doing
> that.
Ripping out cache merging entirely for the benefit of an interface seems
like overkill, it actually allows the allocator to return cache-hot
objects that has a small but measurable impact on performance for some
networking loads. It would probably be better to increase awareness of
slabinfo -a and the use of slub_nomerge on the command line when debugging
issues. The most complete solution would be to move everything out of
struct kmem_cache except what is necessary for slabinfo and then point to
the actual cache data structure that could be shared by merged caches.
That's not hard to do, but would add an increment to both the alloc and
free fastpaths and require some surgery throughout all of the slub code to
understand the new data structures and that would be a pretty big patch.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
