From: Andrew Morton <akpm@linux-foundation.org>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Deinline a few functions in mmap.c
Date: Tue, 22 Jul 2008 02:37:04 -0700 [thread overview]
Message-ID: <20080722023704.944efd72.akpm@linux-foundation.org> (raw)
In-Reply-To: <200807051837.30219.vda.linux@googlemail.com>
On Sat, 5 Jul 2008 18:37:30 +0200 Denys Vlasenko <vda.linux@googlemail.com> wrote:
> __vma_link_file and expand_downwards functions are not small,
> yeat they are marked inline. They probably had one callsite
> sometime in the past, but now they have more.
> In order to prevent similar thing, I also deinlined
> expand_upwards, despite it having only pne callsite.
> Nowadays gcc auto-inlines such static functions anyway.
> In find_extend_vma, I removed one extra level of indirection.
>
> Patch is deliberately generated with -U $BIGNUM to make
> it easier to see that functions are big.
>
> Result:
>
> # size */*/mmap.o */vmlinux
> text data bss dec hex filename
> 9514 188 16 9718 25f6 0.org/mm/mmap.o
> 9237 188 16 9441 24e1 deinline/mm/mmap.o
> 6124402 858996 389480 7372878 70804e 0.org/vmlinux
> 6124113 858996 389480 7372589 707f2d deinline/vmlinux
>
So I left this so long that the patch doesn't vaguely apply any more on
-mm, at least. The large amounts of context didn't help.
I had a go at fixing it, but I can't even compile test it because this
morning's linux-next pull was a complete wreck. Maybe tomorrow...
--
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>
prev parent reply other threads:[~2008-07-22 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 16:37 Denys Vlasenko
2008-07-05 17:10 ` Christoph Hellwig
2008-07-22 9:37 ` Andrew Morton [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=20080722023704.944efd72.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vda.linux@googlemail.com \
/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