From: "Christoph Lameter (Ampere)" <cl@linux.com>
To: Chengming Zhou <zhouchengming@bytedance.com>
Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Pekka Enberg <penberg@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mm/slub: directly load freelist from cpu partial slab in the likely case
Date: Thu, 18 Jan 2024 14:14:17 -0800 (PST) [thread overview]
Message-ID: <a2132c63-99a5-7fa2-9f2a-cccf6b40fe9e@linux.com> (raw)
In-Reply-To: <412b8618-0941-4d9d-85df-ee480695e7f7@bytedance.com>
On Thu, 18 Jan 2024, Chengming Zhou wrote:
> So get_freelist() has two cases to handle: cpu slab and cpu partial list slab.
> The latter is NOT frozen, so need to remove "VM_BUG_ON(!new.frozen)" from it.
Right so keep the check if it is the former?
next prev parent reply other threads:[~2024-01-18 22:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 11:45 [PATCH 0/3] mm/slub: some minor optimization and cleanup Chengming Zhou
2024-01-17 11:45 ` [PATCH 1/3] mm/slub: directly load freelist from cpu partial slab in the likely case Chengming Zhou
2024-01-17 22:41 ` Christoph Lameter (Ampere)
2024-01-18 11:37 ` Chengming Zhou
2024-01-18 22:14 ` Christoph Lameter (Ampere) [this message]
2024-01-19 3:53 ` Chengming Zhou
2024-01-22 17:13 ` Vlastimil Babka
2024-01-23 2:51 ` Chengming Zhou
2024-01-23 7:42 ` Chengming Zhou
2024-01-23 8:24 ` Vlastimil Babka
2024-01-23 9:17 ` Chengming Zhou
2024-01-17 11:45 ` [PATCH 2/3] mm/slub: remove full list manipulation for non-debug slab Chengming Zhou
2024-01-17 22:44 ` Christoph Lameter (Ampere)
2024-01-23 8:45 ` Vlastimil Babka
2024-01-17 11:46 ` [PATCH 3/3] mm/slub: remove unused parameter in next_freelist_entry() Chengming Zhou
2024-01-23 8:47 ` 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=a2132c63-99a5-7fa2-9f2a-cccf6b40fe9e@linux.com \
--to=cl@linux.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--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