linux-kernel - Re: [rfc] SLQB: YASA

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20080403171626.0283.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Date:	Thu, 03 Apr 2008 17:17:39 +0900
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Nick Piggin <npiggin@...e.de>
Cc:	kosaki.motohiro@...fujitsu.com,
	Pekka Enberg <penberg@...helsinki.fi>,
	Linux Memory Management List <linux-mm@...ck.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Christoph Lameter <clameter@....com>
Subject: Re: [rfc] SLQB: YASA

Hi 

> > Why is this not a patch set against SLUB?
> 
> It's a completely different design of the core allocator algorithms
> really.
> 
> It probably looks quite similar because I started with slub.c, but
> really is just the peripheral supporting code and structure. I'm never
> intending to try to go through the pain of incrementally changing SLUB
> into SLQB. If SLQB is found to be a good idea, then it could maybe get
> merged.

Do you have performance mesurement result?
I hope see it if possible.

Thanks! :)


--
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/