linux-kernel - Re: [RFC] SLUB - define OO_ macro instead of hardcoded numbers

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: <48FF6800.20705@cs.helsinki.fi>
Date:	Wed, 22 Oct 2008 20:50:56 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Christoph Lameter <cl@...ux-foundation.org>
CC:	Cyrill Gorcunov <gorcunov@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] SLUB - define OO_ macro instead of hardcoded numbers

Christoph Lameter wrote:
> On Wed, 22 Oct 2008, Cyrill Gorcunov wrote:
> 
>> Christoph how about this one?
> 
> Ok. Looks a bit better but we still have two maxes here
> 
> s->max which refers to the maximum number of objects per slab page for a 
> specific slab cache (depends on the runtime configuration). OO_MAX_OBJS 
> refers to the maximum number of objects per slab page that any slab 
> cache can be configured for which is a compile time limit.
> 
> Maybe this is okay, Pekka?

Maybe call the page->objects maximum MAX_OBJS_PER_PAGE as it's not 
strictly related to the other OO code?

		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/