From: Dave Jiang <dave.jiang@intel.com>
To: chengming.zhou@linux.dev, dan.j.williams@intel.com,
vishal.l.verma@intel.com
Cc: nvdimm@lists.linux.dev, linux-cxl@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] dax: remove SLAB_MEM_SPREAD flag usage
Date: Tue, 27 Feb 2024 09:29:20 -0700 [thread overview]
Message-ID: <b9966efa-8efe-4de7-b962-a6edcf2f6904@intel.com> (raw)
In-Reply-To: <20240224134728.829289-1-chengming.zhou@linux.dev>
On 2/24/24 6:47 AM, 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.
Can you please provide a Link tag to the lore post that indicates SLAB_MEM_SPREAD flag is now a no-op?
>
> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
> ---
> drivers/dax/super.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dax/super.c b/drivers/dax/super.c
> index 54e528779877..cff0a15b7236 100644
> --- a/drivers/dax/super.c
> +++ b/drivers/dax/super.c
> @@ -547,7 +547,7 @@ static int dax_fs_init(void)
>
> dax_cache = kmem_cache_create("dax_cache", sizeof(struct dax_device), 0,
> (SLAB_HWCACHE_ALIGN|SLAB_RECLAIM_ACCOUNT|
> - SLAB_MEM_SPREAD|SLAB_ACCOUNT),
> + SLAB_ACCOUNT),
> init_once);
> if (!dax_cache)
> return -ENOMEM;
prev parent reply other threads:[~2024-02-27 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:47 chengming.zhou
2024-02-27 16:29 ` Dave Jiang [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=b9966efa-8efe-4de7-b962-a6edcf2f6904@intel.com \
--to=dave.jiang@intel.com \
--cc=Xiongwei.Song@windriver.com \
--cc=chengming.zhou@linux.dev \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nvdimm@lists.linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=vishal.l.verma@intel.com \
--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