[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190416205212.5cb286fbeec801f50269b2b5@linux-foundation.org>
Date: Tue, 16 Apr 2019 20:52:12 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mel Gorman <mgorman@...hsingularity.net>
Cc: David Rientjes <rientjes@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>,
"Tobin C. Harding" <tobin@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Tejun Heo <tj@...nel.org>, Qian Cai <cai@....pw>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Jesper Dangaard Brouer <brouer@...hat.com>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH 0/1] mm: Remove the SLAB allocator
On Fri, 12 Apr 2019 12:28:16 +0100 Mel Gorman <mgorman@...hsingularity.net> wrote:
> On Wed, Apr 10, 2019 at 02:53:34PM -0700, David Rientjes wrote:
> > > FWIW, our enterprise kernel use it (latest is 4.12 based), and openSUSE
> > > kernels as well (with openSUSE Tumbleweed that includes latest
> > > kernel.org stables). AFAIK we don't enable SLAB_DEBUG even in general
> > > debug kernel flavours as it's just too slow.
> > >
> > > IIRC last time Mel evaluated switching to SLUB, it wasn't a clear
> > > winner, but I'll just CC him for details :)
> > >
> >
> > We also use CONFIG_SLAB and disable CONFIG_SLAB_DEBUG for the same reason.
>
> Would it be possible to re-evaluate using mainline kernel 5.0?
I have vague memories that slab outperforms slub for some networking
loads. Could the net folks please comment?
Powered by blists - more mailing lists