From: David Howells <dhowells@redhat.com>
To: Matt Mackall <mpm@selenic.com>
Cc: dhowells@redhat.com, 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: Wed, 01 Oct 2008 16:00:01 +0100 [thread overview]
Message-ID: <5183.1222873201@redhat.com> (raw)
In-Reply-To: <1222818570.13453.5.camel@calx>
Matt Mackall <mpm@selenic.com> wrote:
> (This applies on top of Nick's second tiny-shmem patch, which hasn't
> made it to mainline yet(!). But as this deletes tiny-shmem.c, you can
> probably ignore the rejects.)
>
> tiny-shmem shares most of its 130 lines of code with shmem and tends
> to break when particular bits of shmem get modified. Unifying saves
> code and makes keeping these two in sync much easier.
>
> before:
> 14367 392 24 14783 39bf mm/shmem.o
> 396 72 8 476 1dc mm/tiny-shmem.o
>
> after:
> 14367 392 24 14783 39bf mm/shmem.o
> 412 72 8 492 1ec mm/shmem.o tiny
>
> Signed-off-by: Matt Mackall <mpm@selenic.com>
Works with my test program:
http://people.redhat.com/~dhowells/doshm.c
Compile and run:
doshm sysv
warthog>size mm/tiny-shmem.o
text data bss dec hex filename
788 36 4 828 33c mm/tiny-shmem.o
warthog>size mm/shmem.o
text data bss dec hex filename
832 36 4 872 368 mm/shmem.o
Acked-by: David Howells <dhowells@redhat.com>
next prev parent reply other threads:[~2008-10-01 15:05 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 [this message]
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
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=5183.1222873201@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox