All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alim Akhtar <alim.akhtar@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: linux-samsung-soc@vger.kernel.org, javier@osg.samsung.com,
	k.kozlowski@samsung.com, kgene@kernel.org
Subject: Re: [RFC PATCH] ARM: exynos_defconfig: Increase CONFIG_BLK_DEV_RAM_SIZE to 64K
Date: Wed, 21 Oct 2015 10:26:56 +0530	[thread overview]
Message-ID: <56271B18.7030000@samsung.com> (raw)
In-Reply-To: <4039144.iLSv7qv3SU@wuerfel>

Hi Arnd

On 10/19/2015 06:52 PM, Arnd Bergmann wrote:
> On Monday 19 October 2015 16:18:35 Alim Akhtar wrote:
>> Spam Status: CRM114
>> 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>
>> ---
>> 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.
>
> Is there still a reason to use ramdisks these days? If 8MB is not
> enough to have a useful initrd, that might mean that everyone else
> uses initramfs and you should just do the same thing?
>
There is not specific reason to still use ramdisks, but I feel till we 
remove this config, lets modify it to be used by few like me.
I am ok with either way.
Thanks
> Then we can also remove this option here.
>
> 	Arnd
>

WARNING: multiple messages have this Message-ID (diff)
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: Wed, 21 Oct 2015 10:26:56 +0530	[thread overview]
Message-ID: <56271B18.7030000@samsung.com> (raw)
In-Reply-To: <4039144.iLSv7qv3SU@wuerfel>

Hi Arnd

On 10/19/2015 06:52 PM, Arnd Bergmann wrote:
> On Monday 19 October 2015 16:18:35 Alim Akhtar wrote:
>> Spam Status: CRM114
>> 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>
>> ---
>> 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.
>
> Is there still a reason to use ramdisks these days? If 8MB is not
> enough to have a useful initrd, that might mean that everyone else
> uses initramfs and you should just do the same thing?
>
There is not specific reason to still use ramdisks, but I feel till we 
remove this config, lets modify it to be used by few like me.
I am ok with either way.
Thanks
> Then we can also remove this option here.
>
> 	Arnd
>

  reply	other threads:[~2015-10-21  5:06 UTC|newest]

Thread overview: 16+ 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 10:48 ` Alim Akhtar
2015-10-19 11:48 ` Javier Martinez Canillas
2015-10-19 11:48   ` Javier Martinez Canillas
2015-10-19 11:51   ` Russell King - ARM Linux
2015-10-19 11:51     ` Russell King - ARM Linux
2015-10-19 11:53     ` Alim Akhtar
2015-10-19 11:53       ` Alim Akhtar
2015-10-19 12:06     ` Javier Martinez Canillas
2015-10-19 12:06       ` Javier Martinez Canillas
2015-10-19 11:55   ` Alim Akhtar
2015-10-19 11:55     ` Alim Akhtar
2015-10-19 13:22 ` Arnd Bergmann
2015-10-19 13:22   ` Arnd Bergmann
2015-10-21  4:56   ` Alim Akhtar [this message]
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=56271B18.7030000@samsung.com \
    --to=alim.akhtar@samsung.com \
    --cc=arnd@arndb.de \
    --cc=javier@osg.samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.