From: "Christoph Lameter (Ampere)" <cl@linux.com>
To: Jianfeng Wang <jianfeng.w.wang@oracle.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"penberg@kernel.org" <penberg@kernel.org>,
"rientjes@google.com" <rientjes@google.com>,
"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Junxiao Bi <junxiao.bi@oracle.com>
Subject: Re: [PATCH] slub: limit number of slabs to scan in count_partial()
Date: Mon, 15 Apr 2024 09:20:29 -0700 (PDT) [thread overview]
Message-ID: <bb1d4c3e-0c1a-0868-5c1f-9a1de8692db1@linux.com> (raw)
In-Reply-To: <5552D041-8549-4E76-B3EC-03C76C117077@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Sat, 13 Apr 2024, Jianfeng Wang wrote:
>>>>>> kmem_cache_shrink() will explicitly sort the partial lists to put the
>>>>>> partial pages in that order.
>>>>>>
>
> Realized that I’d do "echo 1 > /sys/kernel/slab/dentry/shrink” to sort the list explicitly.
> After that, the numbers become:
> N = 10000 -> diff = 7.1 %
> N = 20000 -> diff = 5.7 %
> N = 25000 -> diff = 5.4 %
> So, expecting ~5-7% difference after shrinking.
That still looks ok to me.
next prev parent reply other threads:[~2024-04-15 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 16:40 [PATCH] slub: limit number of slabs to scan in count_partial() Jianfeng Wang
2024-04-11 17:02 ` Christoph Lameter (Ampere)
2024-04-12 7:48 ` Vlastimil Babka
2024-04-12 17:29 ` [External] : " Jianfeng Wang
2024-04-12 18:16 ` Christoph Lameter (Ampere)
2024-04-12 18:32 ` Jianfeng Wang
2024-04-12 20:20 ` [External] : " Vlastimil Babka
2024-04-12 20:44 ` Jianfeng Wang
2024-04-13 1:17 ` Jianfeng Wang
2024-04-15 7:35 ` Vlastimil Babka
2024-04-16 18:58 ` Jianfeng Wang
2024-04-16 20:14 ` Vlastimil Babka
2024-04-15 16:20 ` Christoph Lameter (Ampere) [this message]
2024-04-13 4:43 ` [External] : " Matthew Wilcox
2024-04-12 7:41 ` 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=bb1d4c3e-0c1a-0868-5c1f-9a1de8692db1@linux.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jianfeng.w.wang@oracle.com \
--cc=junxiao.bi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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