From: Chengming Zhou <chengming.zhou@linux.dev>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: chandan.babu@oracle.com, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, vbabka@suse.cz,
roman.gushchin@linux.dev, Xiongwei.Song@windriver.com,
Chengming Zhou <zhouchengming@bytedance.com>
Subject: Re: [PATCH] xfs: remove SLAB_MEM_SPREAD flag usage
Date: Sun, 25 Feb 2024 12:50:18 +0800 [thread overview]
Message-ID: <ed50835c-80be-491f-a5f9-9a669a84cac5@linux.dev> (raw)
In-Reply-To: <20240224170306.GI616564@frogsfrogsfrogs>
On 2024/2/25 01:03, Darrick J. Wong wrote:
> On Sat, Feb 24, 2024 at 01:53:23PM +0000, 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.
>>
>> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
>
> Acked-by: Darrick J. Wong <djwong@kernel.org>
>
> (acked, as in "this looks right, i don't know why it wasn't removed when
> slab went away, and from the -mm list traffic this seems to be in line
> with [1] but i still had to dig for details)
Right, I think it was just forgotten when slab went away. Then Steven reported
this when he found it obsolete. As discussed in [1], we submit these patches
independently to remove its usages.
[1] https://lore.kernel.org/all/20240220-slab-cleanup-flags-v1-0-e657e373944a@suse.cz/
Thanks!
>
> [1] https://lore.kernel.org/linux-mm/20240131172027.10f64405@gandalf.local.home/T/#u
>
> --D
>
>> ---
>> fs/xfs/xfs_super.c | 7 +++----
>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>
>> diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
>> index 56006b877a5d..171a1287b296 100644
>> --- a/fs/xfs/xfs_super.c
>> +++ b/fs/xfs/xfs_super.c
>> @@ -2042,8 +2042,7 @@ xfs_init_caches(void)
>>
>> xfs_buf_cache = kmem_cache_create("xfs_buf", sizeof(struct xfs_buf), 0,
>> SLAB_HWCACHE_ALIGN |
>> - SLAB_RECLAIM_ACCOUNT |
>> - SLAB_MEM_SPREAD,
>> + SLAB_RECLAIM_ACCOUNT,
>> NULL);
>> if (!xfs_buf_cache)
>> goto out;
>> @@ -2108,14 +2107,14 @@ xfs_init_caches(void)
>> sizeof(struct xfs_inode), 0,
>> (SLAB_HWCACHE_ALIGN |
>> SLAB_RECLAIM_ACCOUNT |
>> - SLAB_MEM_SPREAD | SLAB_ACCOUNT),
>> + SLAB_ACCOUNT),
>> xfs_fs_inode_init_once);
>> if (!xfs_inode_cache)
>> goto out_destroy_efi_cache;
>>
>> xfs_ili_cache = kmem_cache_create("xfs_ili",
>> sizeof(struct xfs_inode_log_item), 0,
>> - SLAB_RECLAIM_ACCOUNT | SLAB_MEM_SPREAD,
>> + SLAB_RECLAIM_ACCOUNT,
>> NULL);
>> if (!xfs_ili_cache)
>> goto out_destroy_inode_cache;
>> --
>> 2.40.1
>>
>>
prev parent reply other threads:[~2024-02-25 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:53 [PATCH] xfs: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-24 17:03 ` Darrick J. Wong
2024-02-25 4:50 ` Chengming Zhou [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=ed50835c-80be-491f-a5f9-9a669a84cac5@linux.dev \
--to=chengming.zhou@linux.dev \
--cc=Xiongwei.Song@windriver.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=zhouchengming@bytedance.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.