linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: <chengming.zhou@linux.dev>, <richard@nod.at>
Cc: <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>,
	Chengming Zhou <zhouchengming@bytedance.com>
Subject: Re: [PATCH] ubifs: remove SLAB_MEM_SPREAD flag usage
Date: Mon, 26 Feb 2024 10:12:46 +0800	[thread overview]
Message-ID: <3384a81a-e6c9-6f2e-e66e-c9b9a9433c0f@huawei.com> (raw)
In-Reply-To: <20240224135217.830331-1-chengming.zhou@linux.dev>

在 2024/2/24 21:52, 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/ubifs/super.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 

Reviewed-by: Zhihao Cheng <chengzhihao1@huawei.com>
> diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
> index f780729eec06..8ae7648021a8 100644
> --- a/fs/ubifs/super.c
> +++ b/fs/ubifs/super.c
> @@ -2433,8 +2433,8 @@ static int __init ubifs_init(void)
>   
>   	ubifs_inode_slab = kmem_cache_create("ubifs_inode_slab",
>   				sizeof(struct ubifs_inode), 0,
> -				SLAB_MEM_SPREAD | SLAB_RECLAIM_ACCOUNT |
> -				SLAB_ACCOUNT, &inode_slab_ctor);
> +				SLAB_RECLAIM_ACCOUNT | SLAB_ACCOUNT,
> +				&inode_slab_ctor);
>   	if (!ubifs_inode_slab)
>   		return -ENOMEM;
>   
> 



      parent reply	other threads:[~2024-02-26  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 13:52 chengming.zhou
2024-02-25 20:36 ` Richard Weinberger
2024-02-26  2:12 ` 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=3384a81a-e6c9-6f2e-e66e-c9b9a9433c0f@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=Xiongwei.Song@windriver.com \
    --cc=chengming.zhou@linux.dev \
    --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