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: <1234748316.5669.222.camel@calx>
Date:	Sun, 15 Feb 2009 19:38:36 -0600
From:	Matt Mackall <mpm@...enic.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	"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 Sun, 2009-02-15 at 17:00 -0800, Andrew Morton wrote:
> On Sun, 15 Feb 2009 17:49:41 -0600 Matt Mackall <mpm@...enic.com> wrote:

> The whole concept is quite hacky and nasty, isn't it?.

It is, which is part of why we were trying to kill it. The primary users
were thing growing buffers ala realloc. So we were pushing to change the
callers to just do a realloc. But IPSEC doesn't fit well into that mold.

The fundamental problem here for networking is that 1500 is not very
close to a power of two and just about everything in the VM wants it to
be. If we could get SKBs fitting more nicely in memory, I think it would
cease to be a concern.

-- 
http://selenic.com : development and support for Mercurial and Linux

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