public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Dave Young <dyoung@redhat.com>,
	akpm@linux-foundation.org, gregkh@linuxfoundation.org,
	grant.likely@secretlab.ca, sebastian.capella@linaro.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use initmpfs even if there's root= cmdline
Date: Wed, 18 Dec 2013 11:51:30 -0600	[thread overview]
Message-ID: <52B1E0A2.2030202@landley.net> (raw)
In-Reply-To: <20131213023814.GA5519@dhcp-16-126.nay.redhat.com>



On 12/12/13 20:38, Dave Young wrote:
> On 12/12/13 at 05:25pm, Dave Young wrote:
>>
>> Current code use ramfs instead of tmpfs for stub when root= defined.
>>
>> But for real use case with initramfs, usually there's like cmdline like
>> root=UUID=$UUID the root dev is the real device. For that case we have
>> no way to use initmpfs, thus this patch removes the limitation so tmpfs
>> can benefit more people.

The reason I did that was if you specify a root= then you don't want to 
_stay_ on rootfs. You specify root= so either the kernel does 
switch_root for you, or so rootfs does a swich_root at the end.

The point of initmpfs is that when rootfs _is_ the "real" root device, 
it can benefit from being tmpfs. When you're just goign to switch to a 
different root device, tmpfs doesn't make much difference.

> Discussed with Vivek Goyal about the kdump use case, I missed one thing that
> tmpfs has default size limit though we can tune it.
>
> So I will think more about it, will address this later, please ignore this
> patch.

I have a vague todo item of feeding rootflags= through to initmpfs, but 
that's really intended to specify flags for root=. There isn't really an 
existing command line option to specify initramfs flags because ramfs 
doesn't care.

It was one of those "only parse rootflags= for initmpfs when there's no 
root=" vs "create a new rdrootflags= ala rdinit= even though that's a 
subtly wrong name these days..." and it went on the todo list because 
neither approach was obviously superior.

Happy to take suggestions and whip up a patch if this is inconveniencing 
somebody. :)

> Thanks
> Dave

Rob

  reply	other threads:[~2013-12-18 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12  9:25 [PATCH] use initmpfs even if there's root= cmdline Dave Young
2013-12-12 11:49 ` Dave Young
2013-12-13  2:38 ` Dave Young
2013-12-18 17:51   ` Rob Landley [this message]
2013-12-19  2:35     ` Dave Young
2013-12-23  4:49       ` Rob Landley
2013-12-23  6:43         ` Dave Young

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=52B1E0A2.2030202@landley.net \
    --to=rob@landley.net \
    --cc=akpm@linux-foundation.org \
    --cc=dyoung@redhat.com \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian.capella@linaro.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