From: Zhihao Cheng <chengzhihao1@huawei.com>
To: <chengming.zhou@linux.dev>, <dwmw2@infradead.org>,
<richard@nod.at>, <jack@suse.cz>, <chuck.lever@oracle.com>,
<dave.kleikamp@oracle.com>, <amir73il@gmail.com>
Cc: <zhouchengming@bytedance.com>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<vbabka@suse.cz>, <roman.gushchin@linux.dev>,
<Xiongwei.Song@windriver.com>
Subject: Re: [PATCH] jffs2: remove SLAB_MEM_SPREAD flag usage
Date: Mon, 26 Feb 2024 10:13:13 +0800 [thread overview]
Message-ID: <dac3e4b6-2915-7d77-f5d4-4ba8d510d952@huawei.com> (raw)
In-Reply-To: <20240224134915.829634-1-chengming.zhou@linux.dev>
在 2024/2/24 21:49, chengming.zhou@linux.dev 写道:
> 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/jffs2/super.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
>
> diff --git a/fs/jffs2/super.c b/fs/jffs2/super.c
> index f99591a634b4..aede1be4dc0c 100644
> --- a/fs/jffs2/super.c
> +++ b/fs/jffs2/super.c
> @@ -387,7 +387,7 @@ static int __init init_jffs2_fs(void)
> jffs2_inode_cachep = kmem_cache_create("jffs2_i",
> sizeof(struct jffs2_inode_info),
> 0, (SLAB_RECLAIM_ACCOUNT|
> - SLAB_MEM_SPREAD|SLAB_ACCOUNT),
> + SLAB_ACCOUNT),
> jffs2_i_init_once);
> if (!jffs2_inode_cachep) {
> pr_err("error: Failed to initialise inode cache\n");
>
prev parent reply other threads:[~2024-02-26 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:49 chengming.zhou
2024-02-26 2:13 ` Zhihao Cheng [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=dac3e4b6-2915-7d77-f5d4-4ba8d510d952@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=Xiongwei.Song@windriver.com \
--cc=amir73il@gmail.com \
--cc=chengming.zhou@linux.dev \
--cc=chuck.lever@oracle.com \
--cc=dave.kleikamp@oracle.com \
--cc=dwmw2@infradead.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--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