linux-kernel - Re: [PATCH] slob: reduce list scanning

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]

Date:	Mon, 16 Jul 2007 18:37:33 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Pekka Enberg <penberg@...helsinki.fi>
CC:	Matt Mackall <mpm@...enic.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	akpm@...ux-foundation.org, Christoph Lameter <clameter@....com>
Subject: Re: [PATCH] slob: reduce list scanning

Pekka Enberg wrote:
> On 7/16/07, Nick Piggin <nickpiggin@...oo.com.au> wrote:
> 
>> Actually SLOB potentially has some fundamental CPU cache hotness
>> advantages over the other allocators, for the same reasons as
>> its space advantages.
> 
> 
> Because consecutive allocations hit the same cache-hot page regardless
> of requested size where as SLUB by definition distributes allocations
> to different pages (some of which may not be hot)?

Yeah, that, and also a newly freed slab object is quite likely to be
hot, and that memory can be used by another subsequent allocation --
not always, because the allocation heuristics may not place it there,
but there is potential that is impossible with slab allocators.

-- 
SUSE Labs, Novell Inc.
-
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/