From: Qian Cai <cai@lca.pw>
To: "Gary B. Genett" <me@garybgenett.net>
Cc: Hugh Dickins <hughd@google.com>, linux-mm@kvack.org
Subject: Re: [PATCH] shmem: add shmem_size option for full filesystem
Date: Wed, 9 Oct 2019 07:12:06 -0400 [thread overview]
Message-ID: <E278467F-D56E-4906-AD8A-1035F3A962D1@lca.pw> (raw)
In-Reply-To: <20191008201710.GA21892@spider>
> On Oct 8, 2019, at 4:17 PM, Gary B. Genett <me@garybgenett.net> wrote:
>
> Adds a kernel configuration option to specify the size of the shmem
> filesystem. It is currently hard-coded to 50% of memory. Users should
> have the option to set this value as they see fit.
>
> A specific case where this would be necessary is if the initramfs were
> larger than half of the memory, such as a 2.5GB "live" filesystem on
> a system with 4GB of memory. Without this option, this causes a kernel
> panic. With this option, the user may specify the number of pages of
> memory they need for their root filesystem.
>
> This patch creates the SHMEM_SIZE configuration option, which is
> specified as the number of memory pages to use for the shmem
> filesystem. The default remains unchanged. This patch has no impact
> unless the values are changed.
>
> The option is marked as expert, and the help text is clear that it
> should only be set if the user knows what they are doing.
Hide it under the EXPERT does not mean the bar is lower to justify when introduced a new config option. What’s the benefits of this vs squashfs/resize?
next prev parent reply other threads:[~2019-10-09 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 20:17 [PATCH] shmem: add shmem_size option for full filesystem Gary B. Genett
2019-10-09 11:12 ` Qian Cai [this message]
2019-10-09 18:45 ` -Gary-
2019-10-09 11:56 ` Vlastimil Babka
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=E278467F-D56E-4906-AD8A-1035F3A962D1@lca.pw \
--to=cai@lca.pw \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=me@garybgenett.net \
/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).