linux-kernel - Re: lockdep complaints in slab allocator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B0CDBDE.8090307@cs.helsinki.fi>
Date:	Wed, 25 Nov 2009 09:25:18 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	David Rientjes <rientjes@...gle.com>,
	Matt Mackall <mpm@...enic.com>, paulmck@...ux.vnet.ibm.com,
	linux-mm@...ck.org, Christoph Lameter <cl@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Nick Piggin <npiggin@...e.de>
Subject: Re: lockdep complaints in slab allocator

Peter Zijlstra kirjoitti:
> Then maybe we should toss SLUB? But then there's people who say SLUB is
> better for them. Without forcing something to happen we'll be stuck with
> multiple allocators forever.

SLUB is good for NUMA, SLAB is pretty much a disaster with it's alien 
tentacles^Hcaches. AFAIK, SLQB hasn't received much NUMA attention so 
it's not obvious whether or not it will be able to perform as well as 
SLUB or not.

The biggest problem with SLUB is that most of the people (excluding 
Christoph and myself) seem to think the design is unfixable for their 
favorite workload so they prefer to either stay with SLAB or work on SLQB.

I really couldn't care less which allocator we end up with as long as 
it's not SLAB. I do think putting more performance tuning effort into 
SLUB would give best results because the allocator is pretty rock solid 
at this point. People seem underestimate the total effort needed to make 
a slab allocator good enough for the general public (which is why I 
think SLQB still has a long way to go).

			Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/