From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Kukjin Kim <kgene@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: exynos_defconfig: Enable DYNAMIC_DEBUG and get rid of old ext3
Date: Mon, 30 Jan 2017 16:35:09 -0300 [thread overview]
Message-ID: <fae36789-d016-8dee-12df-ff896a3373b9@osg.samsung.com> (raw)
In-Reply-To: <20170130192749.3690-1-krzk@kernel.org>
Hello Krzysztof,
On 01/30/2017 04:27 PM, Krzysztof Kozlowski wrote:
> DYNAMIC_DEBUG is quite useful for debugging kernels and should not cause
> noticeable performance regressions. It makes the kernel noticeably
> bigger (around 4%) but this difference should not impact typical
> developer and reference usage of this defconfig.
>
> Sizes:
> zImage-old: 4641496 bytes
> zImage-new: 4811384 bytes
>
> text data bss dec hex filename
> 7031229 2570916 327016 9929161 9781c9 vmlinux-old
> 7205921 2800052 327016 10332989 9dab3d vmlinux-new
>
Agreed, most people usually will end enabling this option when debugging
issues anyways so having enabled by default is quite convenient indeed.
> Additionally, remove the EXT3_FS symbol because it is entirely replaced
> by EXT4_FS.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
prev parent reply other threads:[~2017-01-30 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 19:27 [PATCH] ARM: exynos_defconfig: Enable DYNAMIC_DEBUG and get rid of old ext3 Krzysztof Kozlowski
2017-01-30 19:35 ` Javier Martinez Canillas [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=fae36789-d016-8dee-12df-ff896a3373b9@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).