public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.19-rc1
Date: Sun, 04 Jan 2015 17:46:31 +0100	[thread overview]
Message-ID: <3902724.ayWKVuEiEg@wuerfel> (raw)
In-Reply-To: <20150103134437.GO582@fuloong-minipc.musicnaut.iki.fi>

On Saturday 03 January 2015 15:44:38 Aaro Koskinen wrote:
> 
> On Sat, Jan 03, 2015 at 01:51:53PM +0100, Arnd Bergmann wrote:
> > On Saturday 03 January 2015 07:21:49 Paul Walmsley wrote:
> > > Another ~300KB kernel object size increase for omap2plus_defconfig 
> > > kernels.
> > 
> > 300kb seems like a lot for a single release. Have you looked into
> > where this is coming from?
> 
> In 3.19-rc1, all initrd decompressors are by default enabled...
> 
>  CONFIG_RD_GZIP=y
> -# CONFIG_RD_BZIP2 is not set
> -# CONFIG_RD_LZMA is not set
> -# CONFIG_RD_XZ is not set
> -# CONFIG_RD_LZO is not set
> -# CONFIG_RD_LZ4 is not set
> +CONFIG_RD_BZIP2=y
> +CONFIG_RD_LZMA=y
> +CONFIG_RD_XZ=y
> +CONFIG_RD_LZO=y
> +CONFIG_RD_LZ4=y
> 

Interesting, this seems to be the opposite of the intention of the
change that caused it, which tried to let you disable the algorithms
without selecting CONFIG_EXPERT. For some reason that is impossible
to know now, they already defaulted to 'n' when EXPERT was set, but
now they default to 'y'.

Does this indeed cause the entire change in size?

	Arnd

  reply	other threads:[~2015-01-04 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03  7:21 OMAP baseline test results for v3.19-rc1 Paul Walmsley
2015-01-03 12:51 ` Arnd Bergmann
2015-01-03 13:44   ` Aaro Koskinen
2015-01-04 16:46     ` Arnd Bergmann [this message]
2015-01-04 19:55       ` Aaro Koskinen
2015-01-03 20:28   ` Paul Walmsley
2015-01-04 16:48     ` Arnd Bergmann
2015-01-04 18:44       ` 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=3902724.ayWKVuEiEg@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@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