From: Chengming Zhou <chengming.zhou@linux•dev>
To: horms@kernel•org
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
netdev@vger•kernel.org,
Chengming Zhou <zhouchengming@bytedance•com>
Subject: [PATCH v2] net: remove SLAB_MEM_SPREAD flag usage
Date: Wed, 28 Feb 2024 03:06:58 +0000 [thread overview]
Message-ID: <20240228030658.3512782-1-chengming.zhou@linux.dev> (raw)
In-Reply-To: <20240227170937.GD277116@kernel.org>
From: Chengming Zhou <zhouchengming@bytedance•com>
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 since the commit
16a1d968358a ("mm/slab: remove mm/slab.c and slab_def.h"). 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/
Signed-off-by: Chengming Zhou <zhouchengming@bytedance•com>
---
v2:
- Update the patch description and include the related link to
make it clearer that SLAB_MEM_SPREAD flag is now a no-op.
---
net/socket.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/socket.c b/net/socket.c
index ed3df2f749bf..7e9c8fc9a5b4 100644
--- a/net/socket.c
+++ b/net/socket.c
@@ -343,7 +343,7 @@ static void init_inodecache(void)
0,
(SLAB_HWCACHE_ALIGN |
SLAB_RECLAIM_ACCOUNT |
- SLAB_MEM_SPREAD | SLAB_ACCOUNT),
+ SLAB_ACCOUNT),
init_once);
BUG_ON(sock_inode_cachep == NULL);
}
--
2.40.1
next prev parent reply other threads:[~2024-02-28 3:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:49 [PATCH] net: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-26 8:55 ` Chengming Zhou
2024-02-27 17:09 ` Simon Horman
2024-02-28 3:06 ` Chengming Zhou [this message]
2024-02-28 15:04 ` [PATCH v2] " Simon Horman
2024-02-29 3:50 ` patchwork-bot+netdevbpf
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=20240228030658.3512782-1-chengming.zhou@linux.dev \
--to=chengming.zhou@linux$(echo .)dev \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=zhouchengming@bytedance$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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