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-kernel@vger.kernel.org,
penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, junxiao.bi@oracle.com
Subject: Re: [PATCH] slub: limit number of slabs to scan in count_partial()
Date: Fri, 12 Apr 2024 11:16:10 -0700 (PDT) [thread overview]
Message-ID: <bb2cb21b-0a5e-0154-2a7d-7e630b50aa4a@linux.com> (raw)
In-Reply-To: <a8e208fb-7842-4bca-9d2d-3aae21da030c@oracle.com>
On Fri, 12 Apr 2024, Jianfeng Wang wrote:
>>> Can you run some tests showing the difference between the estimation and
>>> the real count?
>
> Yes.
> On a server with one NUMA node, I create a case that uses many dentry objects.
> For "dentry", the length of partial slabs is slightly above 250000. Then, I
> compare my approach of scanning N slabs from the list's head v.s. the original
> approach of scanning the full list. I do it by getting both results using
> the new and the original count_partial() and printing them in /proc/slabinfo.
>
> N = 10000
> my_result = 4741651
> org_result = 4744966
> diff = (org_result - my_result) / org_result = 0.00069 = 0.069 %
>
> Increasing N further to 25000 will only slight improve the accuracy:
> N = 15000 -> diff = 0.02 %
> N = 20000 -> diff = 0.01 %
> N = 25000 -> diff = -0.017 %
>
> Based on the measurement, I think the difference between the estimation and
> the real count is very limited (i.e. less than 0.1% for N = 10000). The
> benefit is significant: shorter execution time for get_slabinfo(); no more
> soft lockups or crashes caused by count_partial().
Wow. That is good. Maybe decrease N to 1000 instead?
next prev parent reply other threads:[~2024-04-12 18:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 16:40 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) [this message]
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)
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=bb2cb21b-0a5e-0154-2a7d-7e630b50aa4a@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