From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Herbert Xu <herbert@gondor.apana.org.au>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Christoph Lameter <cl@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-crypto@vger.kernel.org, Geert.Uytterhoeven@sonycom.com
Subject: Re: [PATCH] Export symbol ksize()
Date: Sun, 15 Feb 2009 19:38:36 -0600 [thread overview]
Message-ID: <1234748316.5669.222.camel@calx> (raw)
In-Reply-To: <20090215170052.44ee8fd5.akpm@linux-foundation.org>
On Sun, 2009-02-15 at 17:00 -0800, Andrew Morton wrote:
> On Sun, 15 Feb 2009 17:49:41 -0600 Matt Mackall <mpm@selenic.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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-16 1:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 13:21 [PATCH] Export symbol ksize() Kirill A. Shutemov
2009-02-10 13:35 ` Pekka Enberg
2009-02-10 13:46 ` Kirill A. Shutemov
2009-02-10 14:06 ` Pekka J Enberg
2009-02-12 10:43 ` Herbert Xu
2009-02-12 10:45 ` Pekka Enberg
2009-02-12 10:50 ` Herbert Xu
2009-02-12 13:10 ` Nick Piggin
2009-02-12 23:09 ` Herbert Xu
2009-02-12 23:37 ` Matt Mackall
2009-02-13 13:20 ` Nick Piggin
2009-02-13 16:57 ` Kyle Moffett
2009-02-12 15:55 ` Pekka Enberg
2009-02-12 23:09 ` Herbert Xu
2009-02-15 21:36 ` Andrew Morton
2009-02-15 21:43 ` Matt Mackall
2009-02-15 21:55 ` Andrew Morton
2009-02-15 23:49 ` Matt Mackall
2009-02-16 1:00 ` Andrew Morton
2009-02-16 1:21 ` Herbert Xu
2009-02-16 1:28 ` Matt Mackall
2009-02-16 1:52 ` Herbert Xu
2009-02-16 1:54 ` Matt Mackall
2009-02-16 1:57 ` Herbert Xu
2009-02-16 1:38 ` Matt Mackall [this message]
2009-02-17 8:43 ` Geert Uytterhoeven
2009-02-17 16:17 ` Christoph Lameter
2009-02-17 17:03 ` Pekka Enberg
2009-02-17 17:06 ` Christoph Lameter
2009-02-16 13:56 ` Johannes Weiner
2009-02-16 14:09 ` Pekka Enberg
2009-02-16 16:32 ` Joe Perches
2009-02-16 17:29 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1234748316.5669.222.camel@calx \
--to=mpm@selenic.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=kirill@shutemov.name \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).