From: alim.akhtar@samsung.com (Alim Akhtar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: exynos_defconfig: Increase CONFIG_BLK_DEV_RAM_SIZE to 64K
Date: Mon, 19 Oct 2015 17:25:13 +0530 [thread overview]
Message-ID: <5624DA21.80702@samsung.com> (raw)
In-Reply-To: <5624D87D.4090901@osg.samsung.com>
Hi Javier,
On 10/19/2015 05:18 PM, Javier Martinez Canillas wrote:
> Hello Alim,
>
> On 10/19/2015 12:48 PM, Alim Akhtar wrote:
>> CONFIG_BLK_DEV_RAM_SIZE is currently set to 8K, which is a bit on the
>> smaller side, lets bump it up to 64K so that a bigger RAM_DISK can
>> be used with defconfig.
>>
>> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
>> ---
>
> I agree that 8KiB is too small and that should be bumped, I'm also
> not sure what the best size would be but 64KiB sounds reasonable
> to me. So for this patch:
>
> Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
>
Thanks
>> Every time I build exynos_defconfig, I need to manually change RAM_SIZE
>> to match my ramdisk image size. I am not sure what is the best ramdisk size
>> might be, but bumping it to 64K might be a reasonable one.
>>
>
> In case you are interested, I got some stats by doing grep on the ARM
> defconfigs using this [0]. Of course the sizes depends on the platform
> but just to have an idea about what sizes are more popular than others.
>
> SIZE COUNT
> 1024 17
> 8192 43
> 10240 1
> 16384 20
> 20000 25
> 32768 36
> 65536 15
>
This is informative.
> [0]: http://hastebin.com/buqukimede.bash
>
> Best regards,
>
next prev parent reply other threads:[~2015-10-19 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 10:48 [RFC PATCH] ARM: exynos_defconfig: Increase CONFIG_BLK_DEV_RAM_SIZE to 64K Alim Akhtar
2015-10-19 11:48 ` Javier Martinez Canillas
2015-10-19 11:51 ` Russell King - ARM Linux
2015-10-19 11:53 ` Alim Akhtar
2015-10-19 12:06 ` Javier Martinez Canillas
2015-10-19 11:55 ` Alim Akhtar [this message]
2015-10-19 13:22 ` Arnd Bergmann
2015-10-21 4:56 ` Alim Akhtar
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=5624DA21.80702@samsung.com \
--to=alim.akhtar@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).