All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qixuan Wu <wuqixuan@huawei.com>
To: <phillip@squashfs.org.uk>, <corbet@lwn.net>
Cc: <paulmck@linux.vnet.ibm.com>, <akpm@linux-foundation.org>,
	<tglx@linutronix.de>, <cdall@linaro.org>, <mingo@kernel.org>,
	<marc.zyngier@arm.com>, <mchehab@kernel.org>,
	<zohar@linux.vnet.ibm.com>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<squashfs-devel@lists.sourceforge.net>, <wuqixuan@huawei.com>
Subject: [PATCH 0/2] Make squashfs fragments' cache size more configurable
Date: Thu, 19 Oct 2017 07:50:58 +0800	[thread overview]
Message-ID: <1508370660-6343-1-git-send-email-wuqixuan@huawei.com> (raw)

Hi All,

Currently, squashfs fragments' cache size is only determined by
config option CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE. Users have
no way to change the value when they get the binary kernel.
Now make it be configured when booting or inserting module.
Actually, it's better that a config option in a number format
in .config file cat be reconfigured during booting or inserting
module.

Thanks
Qixuan

Qixuan Wu (2):
  Squashfs: Let the number of fragments cached configurable
  Documentation/kernel-parameters.txt: Add kernel parameter of squashfs
    fragments' cache size

 Documentation/admin-guide/kernel-parameters.txt |  7 ++++
 fs/squashfs/super.c                             | 43 ++++++++++++++++++++++++-
 2 files changed, 49 insertions(+), 1 deletion(-)

-- 
2.7.4

             reply	other threads:[~2017-10-18  7:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 23:50 Qixuan Wu [this message]
2017-10-18 23:50 ` [PATCH 1/2] Squashfs: Let the number of fragments cached configurable Qixuan Wu
2017-10-18 23:51 ` [PATCH 2/2] Documentation/kernel-parameters.txt: Add kernel parameter of squashfs fragments' cache size Qixuan Wu
2017-10-20  6:18 ` [PATCH 0/2] Make squashfs fragments' cache size more configurable Phillip Lougher
2017-10-20 10:45   ` Wuqixuan

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=1508370660-6343-1-git-send-email-wuqixuan@huawei.com \
    --to=wuqixuan@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=cdall@linaro.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mchehab@kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=phillip@squashfs.org.uk \
    --cc=squashfs-devel@lists.sourceforge.net \
    --cc=tglx@linutronix.de \
    --cc=zohar@linux.vnet.ibm.com \
    /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.