From: Matt Mackall <mpm@selenic.com>
To: David Howells <dhowells@redhat.com>
Cc: Hugh Dickins <hugh@veritas.com>, Nick Piggin <npiggin@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: unify shmem and tiny-shmem
Date: Thu, 02 Oct 2008 17:44:02 -0500 [thread overview]
Message-ID: <1222987442.13453.89.camel@calx> (raw)
In-Reply-To: <1710.1222986220@redhat.com>
On Thu, 2008-10-02 at 23:23 +0100, David Howells wrote:
> Hugh Dickins <hugh@veritas.com> wrote:
>
> > That's much nicer than I'd been imagining, thanks Matt: I've no qualms
> > about the few #ifdefs you're adding to mm/shmem.c, it does seem an
> > outright improvement that you're bringing them together.
>
> It's not an outright improvement. shmem.o is still larger than tiny-shmem.o,
> albeit not a lot; however, some embedded people really do count the bytes.
Here the difference comes down to 16 bytes for the "if (size < 0)"
check/branch, which is a worthwhile check.
> > This ifndef is the ugliest part of it: and looking into it, guess
> > what, shmem_get_unmapped_area() hasn't been used since 2.6.20 -
> > that's right, isn't it, David?
>
> Ummm... It seems to be. I think it used to be used by SYSV SHM. Certainly
> deleting that function causes no link problems.
I've got a patch queued to drop it, will post shortly.
--
Mathematics is the supreme nostalgia of our time.
prev parent reply other threads:[~2008-10-02 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 23:49 [PATCH] mm: unify shmem and tiny-shmem Matt Mackall
2008-10-01 15:00 ` David Howells
2008-10-01 18:39 ` Hugh Dickins
2008-10-02 5:38 ` Nick Piggin
2008-10-02 18:57 ` Matt Mackall
2008-10-02 22:23 ` David Howells
2008-10-02 22:44 ` Matt Mackall [this message]
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=1222987442.13453.89.camel@calx \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.