From: Xiubo Li <xiubli@redhat.com>
To: Chengming Zhou <chengming.zhou@linux.dev>,
idryomov@gmail.com, jlayton@kernel.org
Cc: ceph-devel@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] ceph: remove SLAB_MEM_SPREAD flag usage
Date: Mon, 26 Feb 2024 12:23:36 +0800 [thread overview]
Message-ID: <35df81f5-feac-4373-87a3-d3a27ba9c9d4@redhat.com> (raw)
In-Reply-To: <d91e3235-395a-4e63-8ace-c14dfaf0a4fd@linux.dev>
On 2/26/24 10:42, Chengming Zhou wrote:
> On 2024/2/26 09:43, Xiubo Li wrote:
>> Hi Chengming,
>>
>> Thanks for your patch.
>>
>> BTW, could you share the link of the relevant patches to mark this a no-op ?
> 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. 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 for your quick feedback.
BTW, I couldn't find this change in Linus' tree in the master and even
the v6.8-rc1 tag, please see
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/include/linux/slab.h?h=master.
Did I miss something ? Or has this patch been merged ?
- Xiubo
> Thanks!
>
>> Thanks
>>
>> - Xiubo
>>
>> On 2/24/24 21:47, 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>
>>> ---
>>> fs/ceph/super.c | 18 +++++++++---------
>>> 1 file changed, 9 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/fs/ceph/super.c b/fs/ceph/super.c
>>> index 5ec102f6b1ac..4dcbbaa297f6 100644
>>> --- a/fs/ceph/super.c
>>> +++ b/fs/ceph/super.c
>>> @@ -928,36 +928,36 @@ static int __init init_caches(void)
>>> ceph_inode_cachep = kmem_cache_create("ceph_inode_info",
>>> sizeof(struct ceph_inode_info),
>>> __alignof__(struct ceph_inode_info),
>>> - SLAB_RECLAIM_ACCOUNT|SLAB_MEM_SPREAD|
>>> - SLAB_ACCOUNT, ceph_inode_init_once);
>>> + SLAB_RECLAIM_ACCOUNT|SLAB_ACCOUNT,
>>> + ceph_inode_init_once);
>>> if (!ceph_inode_cachep)
>>> return -ENOMEM;
>>> - ceph_cap_cachep = KMEM_CACHE(ceph_cap, SLAB_MEM_SPREAD);
>>> + ceph_cap_cachep = KMEM_CACHE(ceph_cap, 0);
>>> if (!ceph_cap_cachep)
>>> goto bad_cap;
>>> - ceph_cap_snap_cachep = KMEM_CACHE(ceph_cap_snap, SLAB_MEM_SPREAD);
>>> + ceph_cap_snap_cachep = KMEM_CACHE(ceph_cap_snap, 0);
>>> if (!ceph_cap_snap_cachep)
>>> goto bad_cap_snap;
>>> ceph_cap_flush_cachep = KMEM_CACHE(ceph_cap_flush,
>>> - SLAB_RECLAIM_ACCOUNT|SLAB_MEM_SPREAD);
>>> + SLAB_RECLAIM_ACCOUNT);
>>> if (!ceph_cap_flush_cachep)
>>> goto bad_cap_flush;
>>> ceph_dentry_cachep = KMEM_CACHE(ceph_dentry_info,
>>> - SLAB_RECLAIM_ACCOUNT|SLAB_MEM_SPREAD);
>>> + SLAB_RECLAIM_ACCOUNT);
>>> if (!ceph_dentry_cachep)
>>> goto bad_dentry;
>>> - ceph_file_cachep = KMEM_CACHE(ceph_file_info, SLAB_MEM_SPREAD);
>>> + ceph_file_cachep = KMEM_CACHE(ceph_file_info, 0);
>>> if (!ceph_file_cachep)
>>> goto bad_file;
>>> - ceph_dir_file_cachep = KMEM_CACHE(ceph_dir_file_info, SLAB_MEM_SPREAD);
>>> + ceph_dir_file_cachep = KMEM_CACHE(ceph_dir_file_info, 0);
>>> if (!ceph_dir_file_cachep)
>>> goto bad_dir_file;
>>> - ceph_mds_request_cachep = KMEM_CACHE(ceph_mds_request, SLAB_MEM_SPREAD);
>>> + ceph_mds_request_cachep = KMEM_CACHE(ceph_mds_request, 0);
>>> if (!ceph_mds_request_cachep)
>>> goto bad_mds_req;
>>>
next prev parent reply other threads:[~2024-02-26 4:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:47 chengming.zhou
2024-02-26 1:43 ` Xiubo Li
2024-02-26 2:42 ` Chengming Zhou
2024-02-26 4:23 ` Xiubo Li [this message]
2024-02-26 4:30 ` Chengming Zhou
2024-02-26 4:54 ` Xiubo Li
2024-02-26 8:32 ` 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=35df81f5-feac-4373-87a3-d3a27ba9c9d4@redhat.com \
--to=xiubli@redhat.com \
--cc=Xiongwei.Song@windriver.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox