public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
	RCU <rcu@vger.kernel.org>,
	Neeraj upadhyay <Neeraj.Upadhyay@amd.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Hillf Danton <hdanton@sina.com>,
	Joel Fernandes <joel@joelfernandes.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>,
	Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v6 0/6] Reduce synchronize_rcu() latency(v6)
Date: Mon, 11 Mar 2024 09:43:51 +0100	[thread overview]
Message-ID: <Ze7ER232fPpvGssC@pc636> (raw)
In-Reply-To: <63e54cb9-fd08-43c3-9f42-3627198634e8@paulmck-laptop>

On Fri, Mar 08, 2024 at 01:51:29PM -0800, Paul E. McKenney wrote:
> On Fri, Mar 08, 2024 at 06:34:03PM +0100, Uladzislau Rezki (Sony) wrote:
> > This is v6. It is based on the Paul's "dev" branch:
> > 
> > HEAD: f1bfe538c7970283040a7188a291aca9f18f0c42
> > 
> > please note, that patches should be applied from scratch,
> > i.e. the v5 has to be dropped from the "dev".
> > 
> > v5 -> v6:
> >  - Fix a race due to realising a wait-head from the gp-kthread;
> >  - Use our own private workqueue with WQ_MEM_RECLAIM to have
> >    at least one execution context.
> > 
> > v5: https://lore.kernel.org/lkml/20240220183115.74124-1-urezki@gmail.com/
> > v4: https://lore.kernel.org/lkml/ZZ2bi5iPwXLgjB-f@google.com/T/
> > v3: https://lore.kernel.org/lkml/cd45b0b5-f86b-43fb-a5f3-47d340cd4f9f@paulmck-laptop/T/
> > v2: https://lore.kernel.org/all/20231030131254.488186-1-urezki@gmail.com/T/
> > v1: https://lore.kernel.org/lkml/20231025140915.590390-1-urezki@gmail.com/T/
> 
> Queued in place of your earlier series, thank you!
> 
Thank you!

>
> Not urgent, but which rcutorture scenario should be pressed into service
> testing this?
> 
I tested with setting '5*TREE01 5*TREE02 5*TREE03 5*TREE04' apart of that
i used some private test cases. The rcutree.rcu_normal_wake_from_gp=1 has
to be passed also.

Also, "rcuscale" can be used to stress the "cur_ops->sync()" path:

<snip>
#! /usr/bin/env bash

LOOPS=1

for (( i=0; i<$LOOPS; i++ )); do
        tools/testing/selftests/rcutorture/bin/kvm.sh --memory 10G --torture rcuscale \
    --allcpus \
      --kconfig CONFIG_NR_CPUS=64 \
      --kconfig CONFIG_RCU_NOCB_CPU=y \
      --kconfig CONFIG_RCU_NOCB_CPU_DEFAULT_ALL=y \
      --kconfig CONFIG_RCU_LAZY=n \
      --bootargs "rcuscale.nwriters=200 rcuscale.nreaders=220 rcuscale.minruntime=50000 \
                         torture.disable_onoff_at_boot rcutree.rcu_normal_wake_from_gp=1" --trust-make
        echo "Done $i"
done
<snip>

--
Uladzislau Rezki

  reply	other threads:[~2024-03-11  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 17:34 [PATCH v6 0/6] Reduce synchronize_rcu() latency(v6) Uladzislau Rezki (Sony)
2024-03-08 17:34 ` [PATCH v6 1/6] rcu: Add data structures for synchronize_rcu() Uladzislau Rezki (Sony)
2024-03-08 17:34 ` [PATCH v6 2/6] rcu: Reduce synchronize_rcu() latency Uladzislau Rezki (Sony)
2024-03-08 17:34 ` [PATCH v6 3/6] rcu: Add a trace event for synchronize_rcu_normal() Uladzislau Rezki (Sony)
2024-03-08 17:34 ` [PATCH v6 4/6] rcu: Support direct wake-up of synchronize_rcu() users Uladzislau Rezki (Sony)
2024-03-08 17:34 ` [PATCH v6 5/6] rcu: Do not release a wait-head from a GP kthread Uladzislau Rezki (Sony)
2024-03-08 17:34 ` [PATCH v6 6/6] rcu: Allocate WQ with WQ_MEM_RECLAIM bit set Uladzislau Rezki (Sony)
2024-03-08 21:51 ` [PATCH v6 0/6] Reduce synchronize_rcu() latency(v6) Paul E. McKenney
2024-03-11  8:43   ` Uladzislau Rezki [this message]
2024-03-11 19:19     ` Paul E. McKenney

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=Ze7ER232fPpvGssC@pc636 \
    --to=urezki@gmail.com \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=boqun.feng@gmail.com \
    --cc=frederic@kernel.org \
    --cc=hdanton@sina.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksiy.avramchenko@sony.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.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