From: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: Tegra baseline test results for v3.12-rc1
Date: Fri, 4 Oct 2013 00:08:36 -0700 [thread overview]
Message-ID: <524E6974.4040001@nvidia.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1309230703090.18475-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>
Hi Olof,
On 09/23/2013 12:26 AM, Paul Walmsley wrote:
> On Wed, 18 Sep 2013, Olof Johansson wrote:
>
>> On Wed, Sep 18, 2013 at 9:23 AM, Paul Walmsley <pwalmsley-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> wrote:
>>
>>> vmlinux object size
>>> (delta in bytes from test_v3.11-rc7 (d8dfad3876e4386666b759da3c833d62fb8b2267)):
>>> text data bss total kernel
>>> -89208 +10000 -416 -79624 multi_v7_defconfig
>>> +299303 +7244 +1484 +308031 tegra_defconfig
>>>
>> Hm. These deltas are huge. :( It would be interesting to know where
>> they come from.
>
As far as the tegra_defconfig build size deltas go, the short story is:
+ 110KB from v3.11-rc7 to v3.12-rc1, using the same v3.11-rc7
tegra_defconfig
+ 99KB after CONFIG_USB_XHCI_HCD=y
+ 51KB when the various CONFIG_PCI* changes are added
+ 36KB after CONFIG_SYSVIPC=y
+ 10KB after CONFIG_MOUSE_PS2_ELANTECH=y
Details below.
Still need to look into the boot memory size differences.
- Paul
A. v3.11-rc7:
text data bss dec hex filename
7996434 359300 350288 8706022 84d7e6 vmlinux
B. v3.12-rc1 with the v3.11-rc7 tegra_defconfig + 'make oldnoconfig':
text data bss dec hex filename
8101095 364096 351580 8816771 868883 vmlinux (+110KB
from [A])
C. As [B] above, but with CONFIG_USB_XHCI_HCD=y:
text data bss dec hex filename
8199739 364224 351580 8915543 880a57 vmlinux (+209KB
from [A])
D. As [C] above, but with CONFIG_PCI_TEGRA=y:
text data bss dec hex filename
8207431 364288 351580 8923299 8828a3 vmlinux (+217KB
from [A])
E. As [D] above, but with CONFIG_PCIEPORTBUS=y + related defaults:
text data bss dec hex filename
8233007 364856 351644 8949507 888f03 vmlinux (+243KB
from [A])
F. As [E] above, but with CONFIG_PCI_MSI=y:
text data bss dec hex filename
8249233 365128 351644 8966005 88cf75 vmlinux (+260KB
from [A])
G. As [F] above, but with CONFIG_DMA_CMA=y + related defaults:
text data bss dec hex filename
8251161 365184 351772 8968117 88d7b5 vmlinux (+262KB
from [A])
H. As [G] above, but with CONFIG_SYSVIPC=y:
text data bss dec hex filename
8286273 365968 351772 9004013 8963ed vmlinux (+298KB
from [A])
I. As [H] above, but with CONFIG_MOUSE_PS2_ELANTECH=y:
text data bss dec hex filename
8295737 366544 351772 9014053 898b25 vmlinux (+308KB
from [A])
WARNING: multiple messages have this Message-ID (diff)
From: pwalmsley@nvidia.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra baseline test results for v3.12-rc1
Date: Fri, 4 Oct 2013 00:08:36 -0700 [thread overview]
Message-ID: <524E6974.4040001@nvidia.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1309230703090.18475@utopia.booyaka.com>
Hi Olof,
On 09/23/2013 12:26 AM, Paul Walmsley wrote:
> On Wed, 18 Sep 2013, Olof Johansson wrote:
>
>> On Wed, Sep 18, 2013 at 9:23 AM, Paul Walmsley <pwalmsley@nvidia.com> wrote:
>>
>>> vmlinux object size
>>> (delta in bytes from test_v3.11-rc7 (d8dfad3876e4386666b759da3c833d62fb8b2267)):
>>> text data bss total kernel
>>> -89208 +10000 -416 -79624 multi_v7_defconfig
>>> +299303 +7244 +1484 +308031 tegra_defconfig
>>>
>> Hm. These deltas are huge. :( It would be interesting to know where
>> they come from.
>
As far as the tegra_defconfig build size deltas go, the short story is:
+ 110KB from v3.11-rc7 to v3.12-rc1, using the same v3.11-rc7
tegra_defconfig
+ 99KB after CONFIG_USB_XHCI_HCD=y
+ 51KB when the various CONFIG_PCI* changes are added
+ 36KB after CONFIG_SYSVIPC=y
+ 10KB after CONFIG_MOUSE_PS2_ELANTECH=y
Details below.
Still need to look into the boot memory size differences.
- Paul
A. v3.11-rc7:
text data bss dec hex filename
7996434 359300 350288 8706022 84d7e6 vmlinux
B. v3.12-rc1 with the v3.11-rc7 tegra_defconfig + 'make oldnoconfig':
text data bss dec hex filename
8101095 364096 351580 8816771 868883 vmlinux (+110KB
from [A])
C. As [B] above, but with CONFIG_USB_XHCI_HCD=y:
text data bss dec hex filename
8199739 364224 351580 8915543 880a57 vmlinux (+209KB
from [A])
D. As [C] above, but with CONFIG_PCI_TEGRA=y:
text data bss dec hex filename
8207431 364288 351580 8923299 8828a3 vmlinux (+217KB
from [A])
E. As [D] above, but with CONFIG_PCIEPORTBUS=y + related defaults:
text data bss dec hex filename
8233007 364856 351644 8949507 888f03 vmlinux (+243KB
from [A])
F. As [E] above, but with CONFIG_PCI_MSI=y:
text data bss dec hex filename
8249233 365128 351644 8966005 88cf75 vmlinux (+260KB
from [A])
G. As [F] above, but with CONFIG_DMA_CMA=y + related defaults:
text data bss dec hex filename
8251161 365184 351772 8968117 88d7b5 vmlinux (+262KB
from [A])
H. As [G] above, but with CONFIG_SYSVIPC=y:
text data bss dec hex filename
8286273 365968 351772 9004013 8963ed vmlinux (+298KB
from [A])
I. As [H] above, but with CONFIG_MOUSE_PS2_ELANTECH=y:
text data bss dec hex filename
8295737 366544 351772 9014053 898b25 vmlinux (+308KB
from [A])
next prev parent reply other threads:[~2013-10-04 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 16:23 Tegra baseline test results for v3.12-rc1 Paul Walmsley
2013-09-18 16:23 ` Paul Walmsley
[not found] ` <A4DCC42E2B5835498682FCB0A8F9F873378C267FFD-wAPRp6hVlRhDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2013-09-18 22:01 ` Olof Johansson
2013-09-18 22:01 ` Olof Johansson
[not found] ` <CAOesGMjAQZMUdC9ZoGhX=zEA3HCky1zwE0-B6fNAJubqO9bVzw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-23 7:26 ` Paul Walmsley
2013-09-23 7:26 ` Paul Walmsley
[not found] ` <alpine.DEB.2.02.1309230703090.18475-rwI8Ez+7Ko+d5PgPZx9QOdBPR1lH4CV8@public.gmane.org>
2013-10-04 7:08 ` Paul Walmsley [this message]
2013-10-04 7:08 ` Paul Walmsley
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=524E6974.4040001@nvidia.com \
--to=pwalmsley-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.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 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.