From: Chao Yu <chao@kernel.org>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>, linux-erofs@lists.ozlabs.org
Cc: chao@kernel.org, Gao Xiang <xiang@kernel.org>,
Yue Hu <zbestahu@gmail.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
Sandeep Dhavale <dhavale@google.com>,
Hongbo Li <hongbohbli@tencent.com>,
Chunhai Guo <guochunhai@vivo.com>,
linux-kernel@vger.kernel.org, Shirisha G <shirisha@linux.ibm.com>
Subject: Re: [PATCH 1/1] erofs: fix unused pcluster_pools for higher page sizes
Date: Mon, 17 Aug 2026 16:54:37 +0800 [thread overview]
Message-ID: <68fd8196-dabf-4288-bd95-7500a7408c32@kernel.org> (raw)
In-Reply-To: <808f25346aeac628aa9968f786fdbba09366fd76.1786884312.git.ojaswin@linux.ibm.com>
On 8/16/26 21:07, Ojaswin Mujoo wrote:
> pcluster_pool[] hardcodes {1,4,16,64,128,Z_EROFS_PCLUSTER_MAX_PAGES+1},
> but the assumption of Z_EROFS_PCLUSTER_MAX_PAGES == 256 is only right
> for 4k page sizes. For higher page sizes like 16k or 64k, This results
> in us ending up with clusters bigger than what we will ever use, since
> we only support upto 1MB of compressed data. For example, on 64k page
> size we will only ever use clusters with nrpages= 1, 4 and 17.
>
> This patch fixes the allocation for such higher pages sizes by adding
> some compile time checks.
>
> Below are the clusters created right after boot on a 64KB page size
> machine
>
> $cat /proc/slabinfo | grep pcluster | cut -d" " -f1:
>
> Before the patch:
>
> erofs_pcluster-1
> erofs_pcluster-4
> erofs_pcluster-16
> erofs_pcluster-17
> erofs_pcluster-64
> erofs_pcluster-128
>
>
> After the patch:
>
> erofs_pcluster-1
> erofs_pcluster-4
> erofs_pcluster-17
>
> Fixes: 9f6cc76e6ff0 ("erofs: introduce physical cluster slab pools")
> Reported-by: Shirisha G <shirisha@linux.ibm.com>
> Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2026-08-17 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 13:07 [PATCH 0/1] erofs: fix unused pcluster_pools for higher page sizes Ojaswin Mujoo
2026-08-16 13:07 ` [PATCH 1/1] " Ojaswin Mujoo
2026-08-17 1:34 ` Gao Xiang
2026-08-17 8:54 ` Chao Yu [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=68fd8196-dabf-4288-bd95-7500a7408c32@kernel.org \
--to=chao@kernel.org \
--cc=dhavale@google.com \
--cc=guochunhai@vivo.com \
--cc=hongbohbli@tencent.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=shirisha@linux.ibm.com \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox