linux-kernel - Re: [PATCH] Export symbol ksize()

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: <200902140020.45522.nickpiggin@yahoo.com.au>
Date:	Sat, 14 Feb 2009 00:20:44 +1100
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Matt Mackall <mpm@...enic.com>
Cc:	Herbert Xu <herbert@...dor.apana.org.au>,
	Pekka Enberg <penberg@...helsinki.fi>,
	"Kirill A. Shutemov" <kirill@...temov.name>,
	Christoph Lameter <cl@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	linux-crypto@...r.kernel.org, Geert.Uytterhoeven@...ycom.com
Subject: Re: [PATCH] Export symbol ksize()

On Friday 13 February 2009 10:37:01 Matt Mackall wrote:
> On Fri, 2009-02-13 at 07:09 +0800, Herbert Xu wrote:
> > On Fri, Feb 13, 2009 at 12:10:45AM +1100, Nick Piggin wrote:
> > > I would be interested to know how that goes. You always have this
> > > circular issue that if a little more space helps significantly, then
> > > maybe it is a good idea to explicitly ask for those bytes. Of course
> > > that larger allocation is also likely to have some slack bytes.
> >
> > Well, the thing is we don't know apriori whether we need the
> > extra space.  The idea is to use the extra space if available
> > to avoid reallocation when we hit things like IPsec.
>
> I'm not entirely convinced by this argument. If you're concerned about
> space rather than performance, then you want an allocator that doesn't
> waste space in the first place and you don't try to do "sub-allocations"
> by hand. If you're concerned about performance, you instead optimize
> your allocator to be as fast as possible and again avoid conditional
> branches for sub-allocations.

Well, my earlier reasoning is no longer so clear cut if eg. there
are common cases where no extra space is required, but rare cases
where extra space might be a big win if it eg avoids extra
alloc, copy, free or something.

Because even with performance oriented allocators, there is a non-zero
cost to explicitly asking for more memory -- queues tend to get smaller
at larger object sizes, and page allocation orders can increase. So if
it is very uncommon to need extra space you don't want to burden the
common case with it.


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