The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: chenweilong <chenweilong@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <viro@zeniv.linux.org.uk>, <keescook@chromium.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [linux-next] rootfs: rootflags take effect when mount rootfs
Date: Mon, 28 Jun 2021 09:47:53 +0800	[thread overview]
Message-ID: <929b30c6-9d5e-0e57-c2a0-5c166b32dc10@huawei.com> (raw)
In-Reply-To: <YNhW/XQlZxfJR9Us@kroah.com>

On 2021/6/27 18:46, Greg KH wrote:
> On Sat, Jun 26, 2021 at 09:16:55AM +0800, Weilong Chen wrote:
>> The kernel root filesystem may use the rootflags parameters
>> when mount, especially for tmpfs, to setup a variety of features.
>>
>> For example:
>> 1. Add 'rootflags=huge=always' to boot args.
>> 2. When the OS bootup:
>> rootfs on / type rootfs (..., huge=always)
>> Then we can get the hugepage performance improvement of tmpfs.
>>
>> Signed-off-by: Weilong Chen <chenweilong@huawei.com>
>> ---
>>  fs/namespace.c       | 5 +++--
>>  include/linux/init.h | 2 +-
>>  init/do_mounts.c     | 4 +++-
>>  3 files changed, 7 insertions(+), 4 deletions(-)
> No documentation update for this new user/kernel api you added?

There is already relevant documents (Documentation/admin-guide/kernel-parameters.txt)

description:

    rootflags=      [KNL] Set root filesystem mount option string

This patch make it work for tmpfs.

> .



      reply	other threads:[~2021-06-28  1:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-26  1:16 [linux-next] rootfs: rootflags take effect when mount rootfs Weilong Chen
2021-06-27 10:46 ` Greg KH
2021-06-28  1:47   ` chenweilong [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=929b30c6-9d5e-0e57-c2a0-5c166b32dc10@huawei.com \
    --to=chenweilong@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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