From: Brian Norris <computersforpeace@gmail.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: David Woodhouse <David.Woodhouse@intel.com>,
Artem Bityutskiy <Artem.Bityutskiy@linux.intel.com>,
Jingoo Han <jg1.han@samsung.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Aaron Sierra <asierra@xes-inc.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] mtd: cfi: Deiline large functions
Date: Wed, 27 May 2015 12:44:33 -0700 [thread overview]
Message-ID: <20150527194348.GI27753@ld-irv-0074> (raw)
In-Reply-To: <1431946720-32281-1-git-send-email-dvlasenk@redhat.com>
On Mon, May 18, 2015 at 12:58:40PM +0200, Denys Vlasenko wrote:
> With this .config: http://busybox.net/~vda/kernel_config,
> after uninlining these functions have sizes and callsite counts
> as follows:
>
> cfi_udelay(): 74 bytes, 26 callsites
> cfi_send_gen_cmd(): 153 bytes, 95 callsites
> cfi_build_cmd(): 274 bytes, 123 callsites
> cfi_build_cmd_addr(): 49 bytes, 15 callsites
> cfi_merge_status(): 230 bytes, 3 callsites
>
> Reduction in code size is about 50,000:
>
> text data bss dec hex filename
> 85842882 22294584 20627456 128764922 7accbfa vmlinux.before
> 85789648 22294616 20627456 128711720 7abfc28 vmlinux
>
> Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
> CC: Dan Carpenter <dan.carpenter@oracle.com>
> CC: Jingoo Han <jg1.han@samsung.com>
> CC: Brian Norris <computersforpeace@gmail.com>
> CC: Aaron Sierra <asierra@xes-inc.com>
> CC: Artem Bityutskiy <Artem.Bityutskiy@linux.intel.com>
> CC: David Woodhouse <David.Woodhouse@intel.com>
> CC: linux-mtd@lists.infradead.org
> CC: linux-kernel@vger.kernel.org
Fixed the subject and applied to l2-mtd.git.
For my reference, did you test this, or just compile test?
Brian
prev parent reply other threads:[~2015-05-27 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 10:58 [PATCH] mtd: cfi: Deiline large functions Denys Vlasenko
2015-05-20 18:56 ` Brian Norris
2015-05-21 7:50 ` Denys Vlasenko
2015-05-21 8:36 ` Brian Norris
2015-05-21 10:13 ` Denys Vlasenko
2015-05-21 18:03 ` Brian Norris
2015-05-27 19:44 ` Brian Norris [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=20150527194348.GI27753@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=Artem.Bityutskiy@linux.intel.com \
--cc=David.Woodhouse@intel.com \
--cc=asierra@xes-inc.com \
--cc=dan.carpenter@oracle.com \
--cc=dvlasenk@redhat.com \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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