From: Mel Gorman <mgorman@techsingularity.net>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Catalin.Marinas@arm.com, akpm@linux-foundation.org,
aneesh.kumar@linux.ibm.com, bharata@linux.ibm.com, cl@linux.com,
guro@fb.com, hannes@cmpxchg.org, iamjoonsoo.kim@lge.com,
jannh@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@kernel.org, rientjes@google.com,
shakeelb@google.com, vincent.guittot@linaro.org, will@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mm, slub: better heuristic for number of cpus when calculating slab order
Date: Wed, 10 Feb 2021 14:07:12 +0000 [thread overview]
Message-ID: <20210210140712.GB3697@techsingularity.net> (raw)
In-Reply-To: <20210208134108.22286-1-vbabka@suse.cz>
On Mon, Feb 08, 2021 at 02:41:08PM +0100, Vlastimil Babka wrote:
> When creating a new kmem cache, SLUB determines how large the slab pages will
> based on number of inputs, including the number of CPUs in the system. Larger
> slab pages mean that more objects can be allocated/free from per-cpu slabs
> before accessing shared structures, but also potentially more memory can be
> wasted due to low slab usage and fragmentation.
> The rough idea of using number of CPUs is that larger systems will be more
> likely to benefit from reduced contention, and also should have enough memory
> to spare.
>
> <SNIP>
>
> So this patch tries to determine the best available value without specific arch
> knowledge.
> - num_present_cpus() if the number is larger than 1, as that means the arch is
> likely setting it properly
> - nr_cpu_ids otherwise
>
> This should fix the reported regressions while also keeping the effect of
> 045ab8c9487b for PowerPC systems. It's possible there are configurations where
> num_present_cpus() is 1 during boot while nr_cpu_ids is at the same time
> bloated, so these (if they exist) would keep the large orders based on
> nr_cpu_ids as was before 045ab8c9487b.
>
Tested-by: Mel Gorman <mgorman@techsingularity.net>
Only x86-64 tested, three machines, all showing similar results as would
be expected. One example;
hackbench-process-sockets
5.11.0-rc7 5.11.0-rc7 5.11.0-rc7
vanilla revert-v1r1 vbabka-fix-v1r1
Amean 1 0.3873 ( 0.00%) 0.4060 ( -4.82%) 0.3747 ( 3.27%)
Amean 4 1.3767 ( 0.00%) 0.7700 * 44.07%* 0.7790 * 43.41%*
Amean 7 2.4710 ( 0.00%) 1.2753 * 48.39%* 1.2680 * 48.68%*
Amean 12 3.7103 ( 0.00%) 1.9570 * 47.26%* 1.9470 * 47.52%*
Amean 21 5.9790 ( 0.00%) 2.9760 * 50.23%* 2.9830 * 50.11%*
Amean 30 8.0467 ( 0.00%) 4.0590 * 49.56%* 4.0410 * 49.78%*
Amean 48 12.8180 ( 0.00%) 6.5167 * 49.16%* 6.4070 * 50.02%*
Amean 79 20.5150 ( 0.00%) 10.3580 * 49.51%* 10.3740 * 49.43%*
Amean 110 25.5320 ( 0.00%) 14.0453 * 44.99%* 14.0577 * 44.94%*
Amean 141 32.4170 ( 0.00%) 17.3267 * 46.55%* 17.4977 * 46.02%*
Amean 172 40.0883 ( 0.00%) 21.0360 * 47.53%* 21.1480 * 47.25%*
Amean 203 47.2923 ( 0.00%) 25.2367 * 46.64%* 25.4923 * 46.10%*
Amean 234 55.2623 ( 0.00%) 29.0720 * 47.39%* 29.3273 * 46.93%*
Amean 265 61.4513 ( 0.00%) 33.0260 * 46.26%* 33.0617 * 46.20%*
Amean 296 73.2960 ( 0.00%) 36.6920 * 49.94%* 37.2520 * 49.18%*
Comparing just a revert and the patch
5.11.0-rc7 5.11.0-rc7
revert-v1r1 vbabka-fix-v1r1
Amean 1 0.4060 ( 0.00%) 0.3747 ( 7.72%)
Amean 4 0.7700 ( 0.00%) 0.7790 ( -1.17%)
Amean 7 1.2753 ( 0.00%) 1.2680 ( 0.58%)
Amean 12 1.9570 ( 0.00%) 1.9470 ( 0.51%)
Amean 21 2.9760 ( 0.00%) 2.9830 ( -0.24%)
Amean 30 4.0590 ( 0.00%) 4.0410 ( 0.44%)
Amean 48 6.5167 ( 0.00%) 6.4070 ( 1.68%)
Amean 79 10.3580 ( 0.00%) 10.3740 ( -0.15%)
Amean 110 14.0453 ( 0.00%) 14.0577 ( -0.09%)
Amean 141 17.3267 ( 0.00%) 17.4977 * -0.99%*
Amean 172 21.0360 ( 0.00%) 21.1480 ( -0.53%)
Amean 203 25.2367 ( 0.00%) 25.4923 ( -1.01%)
Amean 234 29.0720 ( 0.00%) 29.3273 ( -0.88%)
Amean 265 33.0260 ( 0.00%) 33.0617 ( -0.11%)
Amean 296 36.6920 ( 0.00%) 37.2520 ( -1.53%)
That's a negligible difference and all but one group (141) was within the
noise. Even for 141, it's very marginal and with the degree of overload
at that group count, it can be ignored.
Thanks!
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2021-02-10 14:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 8:27 [RFC PATCH v0] mm/slub: Let number of online CPUs determine the slub page order Bharata B Rao
2020-11-18 11:25 ` Vlastimil Babka
2020-11-18 19:34 ` Roman Gushchin
2020-11-18 19:53 ` David Rientjes
2021-01-20 17:36 ` Vincent Guittot
2021-01-21 5:30 ` Bharata B Rao
2021-01-21 9:09 ` Vincent Guittot
2021-01-21 10:01 ` Christoph Lameter
2021-01-21 10:48 ` Vincent Guittot
2021-01-21 18:19 ` Vlastimil Babka
2021-01-22 8:03 ` Vincent Guittot
2021-01-22 12:03 ` Vlastimil Babka
2021-01-22 13:16 ` Vincent Guittot
2021-01-23 5:16 ` Bharata B Rao
2021-01-23 12:32 ` Vincent Guittot
2021-01-25 11:20 ` Vlastimil Babka
2021-01-26 23:03 ` Will Deacon
2021-01-27 9:10 ` Christoph Lameter
2021-01-27 11:04 ` Vlastimil Babka
2021-02-03 11:10 ` Bharata B Rao
2021-02-04 7:32 ` Vincent Guittot
2021-02-04 9:07 ` Christoph Lameter
2021-02-04 9:33 ` Vlastimil Babka
2021-02-08 13:41 ` [PATCH] mm, slub: better heuristic for number of cpus when calculating slab order Vlastimil Babka
2021-02-08 14:54 ` Vincent Guittot
2021-02-10 14:07 ` Mel Gorman [this message]
2021-01-22 13:05 ` [RFC PATCH v0] mm/slub: Let number of online CPUs determine the slub page order Jann Horn
2021-01-22 13:09 ` Jann Horn
2021-01-22 15:27 ` Vlastimil Babka
2021-01-25 4:28 ` Bharata B Rao
2021-01-26 8:52 ` Michal Hocko
2021-01-26 13:38 ` Vincent Guittot
2021-01-26 13:59 ` Michal Hocko
2021-01-28 13:45 ` Mel Gorman
2021-01-28 13:57 ` Michal Hocko
2021-01-28 14:42 ` Mel Gorman
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=20210210140712.GB3697@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=Catalin.Marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bharata@linux.ibm.com \
--cc=cl@linux.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=vincent.guittot@linaro.org \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).