From: Chengming Zhou <chengming.zhou@linux.dev>
To: tytso@mit.edu, adilger.kernel@dilger.ca
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
vbabka@suse.cz, roman.gushchin@linux.dev,
Xiongwei.Song@windriver.com
Subject: Re: [PATCH] ext4: remove SLAB_MEM_SPREAD flag usage
Date: Mon, 26 Feb 2024 12:22:04 +0800 [thread overview]
Message-ID: <dd9abbd7-56af-4654-83ae-741d41493f5c@linux.dev> (raw)
In-Reply-To: <20240224134822.829456-1-chengming.zhou@linux.dev>
On 2024/2/24 21:48, chengming.zhou@linux.dev wrote:
> From: Chengming Zhou <zhouchengming@bytedance.com>
>
> The SLAB_MEM_SPREAD flag is already a no-op as of 6.8-rc1, remove
> its usage so we can delete it from slab. No functional change.
Update changelog to make it clearer:
The SLAB_MEM_SPREAD flag used to be implemented in SLAB, which was
removed as of v6.8-rc1, so it became a dead flag since the commit
16a1d968358a ("mm/slab: remove mm/slab.c and slab_def.h"). And the
series[1] went on to mark it obsolete to avoid confusion for users.
Here we can just remove all its users, which has no functional change.
[1] https://lore.kernel.org/all/20240223-slab-cleanup-flags-v2-1-02f1753e8303@suse.cz/
Thanks!
>
> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
> ---
> fs/ext4/super.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index eb689fb85ce9..9a744f22aa24 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -1500,8 +1500,7 @@ static int __init init_inodecache(void)
> {
> ext4_inode_cachep = kmem_cache_create_usercopy("ext4_inode_cache",
> sizeof(struct ext4_inode_info), 0,
> - (SLAB_RECLAIM_ACCOUNT|SLAB_MEM_SPREAD|
> - SLAB_ACCOUNT),
> + SLAB_RECLAIM_ACCOUNT|SLAB_ACCOUNT,
> offsetof(struct ext4_inode_info, i_data),
> sizeof_field(struct ext4_inode_info, i_data),
> init_once);
next prev parent reply other threads:[~2024-02-26 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:48 [PATCH] ext4: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-26 4:22 ` Chengming Zhou [this message]
2024-03-14 3:54 ` Theodore Ts'o
2024-03-14 4:06 ` Matthew Wilcox
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=dd9abbd7-56af-4654-83ae-741d41493f5c@linux.dev \
--to=chengming.zhou@linux.dev \
--cc=Xiongwei.Song@windriver.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
/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.