From: Michael Larabel <Michael@MichaelLarabel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Minchan Kim <minchan@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
Nicolas Saenz Julienne <nsaenzju@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [patch v5] mm: lru_cache_disable: replace work queue synchronization with synchronize_rcu
Date: Sat, 28 May 2022 19:48:06 -0500 [thread overview]
Message-ID: <0ce05ce7-1a00-82df-f37a-bf7f9e216504@MichaelLarabel.com> (raw)
In-Reply-To: <134065a4-0446-bbbc-fca8-59f32798cf08@MichaelLarabel.com>
On 5/28/22 17:54, Michael Larabel wrote:
> On 5/28/22 16:18, Andrew Morton wrote:
>> On Thu, 28 Apr 2022 15:00:11 -0300 Marcelo Tosatti
>> <mtosatti@redhat.com> wrote:
>>
>>> On Thu, Mar 31, 2022 at 03:52:45PM +0200, Borislav Petkov wrote:
>>>> On Thu, Mar 10, 2022 at 10:22:12AM -0300, Marcelo Tosatti wrote:
>>> ...
>>>
>>>> Someone pointed me at this:
>>>>
>>>> https://www.phoronix.com/scan.php?page=news_item&px=Linux-518-Stress-NUMA-Goes-Boom
>>>>
>>>>
>>>> which says this one causes a performance regression with stress-ng's
>>>> NUMA test...
>>> Michael,
>>>
>>> This is probably do_migrate_pages that is taking too long due to
>>> synchronize_rcu().
>>>
>>> Switching to synchronize_rcu_expedited() should probably fix it...
>>> Can you give it a try, please?
>> I guess not.
>>
>> Is anyone else able to demonstrate a stress-ng performance regression
>> due to ff042f4a9b0508? And if so, are they able to try Marcelo's
>> one-liner?
>
>
> Apologies I don't believe I got the email previously (or if it ended
> up in spam or otherwise overlooked) so just noticed this thread now...
>
> I have the system around and will work on verifying it can reproduce
> still and can then test the patch, should be able to get it tomorrow.
>
> Thanks and sorry about the delay.
>
> Michael
>
>
Had a chance to look at it today still. I was able to reproduce the
regression still on that 5950X system going from v5.17 to v5.18 (using
newer stress-ng benchmark and other system changes since the prior
tests). Confirmed it also still showed slower as of today's Git.
I can confirm with Marcelo's patch below that the stress-ng NUMA
performance is back to the v5.17 level of performance (actually, faster)
and certainly not like what I was seeing on v5.18 or Git to this point.
So all seems to be good with that one-liner for the stress-ng NUMA test
case. All the system details and results for those interested is
documented @ https://openbenchmarking.org/result/2205284-PTS-NUMAREGR17
but basically amounts to:
Stress-NG 0.14
Test: NUMA
Bogo Ops/s > Higher Is Better
v5.17: 412.88
v5.18: 49.33
20220528 Git: 49.66
20220528 Git + sched-rcu-exped patch: 468.81
Apologies again about the delay / not seeing the email thread earlier.
Thanks,
Michael
Tested-by: Michael Larabel <Michael@MichaelLarabel.com>
>
>>
>>> diff --git a/mm/swap.c b/mm/swap.c
>>> index bceff0cb559c..04a8bbf9817a 100644
>>> --- a/mm/swap.c
>>> +++ b/mm/swap.c
>>> @@ -879,7 +879,7 @@ void lru_cache_disable(void)
>>> * lru_disable_count = 0 will have exited the critical
>>> * section when synchronize_rcu() returns.
>>> */
>>> - synchronize_rcu();
>>> + synchronize_rcu_expedited();
>>> #ifdef CONFIG_SMP
>>> __lru_add_drain_all(true);
>>> #else
>>>
>>>
next prev parent reply other threads:[~2022-05-29 0:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 16:01 [patch v2] " Marcelo Tosatti
2022-02-22 16:07 ` [patch v3] " Marcelo Tosatti
2022-02-22 16:25 ` Nicolas Saenz Julienne
2022-03-04 1:03 ` Andrew Morton
2022-03-04 1:49 ` Paul E. McKenney
2022-03-04 15:08 ` Marcelo Tosatti
2022-03-04 16:02 ` Paul E. McKenney
2022-03-04 15:11 ` Marcelo Tosatti
2022-03-04 16:29 ` [patch v4] " Marcelo Tosatti
2022-03-05 0:35 ` Andrew Morton
2022-03-07 18:52 ` Marcelo Tosatti
2022-03-10 13:22 ` [patch v5] " Marcelo Tosatti
2022-03-11 2:23 ` Andrew Morton
2022-03-11 8:35 ` Sebastian Andrzej Siewior
2022-03-12 0:40 ` Andrew Morton
2022-03-12 20:39 ` Marcelo Tosatti
2022-03-13 9:23 ` Hillf Danton
2022-03-31 13:52 ` Borislav Petkov
2022-04-28 18:00 ` Marcelo Tosatti
2022-05-28 21:18 ` Andrew Morton
2022-05-28 22:54 ` Michael Larabel
2022-05-29 0:48 ` Michael Larabel [this message]
2022-06-19 12:14 ` Thorsten Leemhuis
2022-06-22 0:15 ` Andrew Morton
2022-03-05 4:33 ` [patch v4] " Paul E. McKenney
2022-03-08 17:41 ` Minchan Kim
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=0ce05ce7-1a00-82df-f37a-bf7f9e216504@MichaelLarabel.com \
--to=michael@michaellarabel.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=minchan@kernel.org \
--cc=mtosatti@redhat.com \
--cc=nsaenzju@redhat.com \
--cc=paulmck@kernel.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.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