mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, josh@freedesktop.org,
	dvhltc@us.ibm.com, niv@us.ibm.com, dino@in.ibm.com,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	vegard.nossum@gmail.com, adobriyan@gmail.com, oleg@tv-sign.ru,
	bunk@kernel.org, rjw@sisk.pl
Subject: Re: [PATCH] Make rcutorture more vicious: reinstate boot-time testing
Date: Thu, 19 Jun 2008 11:29:14 +0200	[thread overview]
Message-ID: <20080619092914.GB15228@elte.hu> (raw)
In-Reply-To: <20080618162649.GA18326@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> Hello again!
> 
> This patch re-institutes the ability to build rcutorture directly into 
> the Linux kernel.  The reason that this capability was removed was 
> that this could result in your kernel being pretty much useless, as 
> rcutorture would be running starting from early boot.  This problem 
> has been avoided by (1) making rcutorture run only three seconds of 
> every six by default, (2) adding a CONFIG_RCU_TORTURE_TEST_RUNNABLE 
> that permits rcutorture to be quiesced at boot time, and (3) adding a 
> sysctl in /proc named /proc/sys/kernel/rcutorture_runnable that 
> permits rcutorture to be quiesced and unquiesced when built into the 
> kernel.
> 
> Please note that this /proc file is -not- available when rcutorture is 
> built as a module.  Please also note that to get the earlier 
> take-no-prisoners behavior, you must use the boot command line to set 
> rcutorture's "stutter" parameter to zero.
> 
> The rcutorture quiescing mechanism is currently quite crude: loops in 
> each rcutorture process that poll a global variable once per tick. 
> Suggestions for improvement are welcome.  The default action will be 
> to reduce the polling rate to a few times per second.

applied to tip/core/rcu - thanks Paul!

FYI, yesterday's rcutorture-stutter feature survived a few hundred 
random bootup tests in -tip testing already.

a possible area for enhancement would be the following code:

static void
rcu_stutter_wait(void)
{
        while (stutter_pause_test || !rcutorture_runnable)
                schedule_timeout_interruptible(1);
}

will cause HZ number of IRQs on nohz systems, even if rcutorture is 
disabled. While it's fine to poll if rcutorture_runnable==1, the sleep 
should be at least 1 second when !rcutorture_runnable.

[ Or it might even make sense to completely stop the threads from a 
  sysctl handler - to make it event-driven and to cause no extra IRQs at 
  all when rcutorture is disabled via /proc. ]

	Ingo

  parent reply	other threads:[~2008-06-19  9:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 12:21 [PATCH] Make rcutorture more vicious: add stutter feature Paul E. McKenney
2008-06-18 13:08 ` Ingo Molnar
2008-06-18 16:26 ` [PATCH] Make rcutorture more vicious: reinstate boot-time testing Paul E. McKenney
2008-06-19  0:42   ` Josh Triplett
2008-06-19  9:29   ` Ingo Molnar [this message]
2008-06-19 15:58     ` Paul E. McKenney
2008-06-19 21:17       ` Randy Dunlap
2008-06-20  5:47         ` Paul E. McKenney
2008-06-21  1:39           ` Randy Dunlap
2008-06-22 20:06   ` [PATCH -tip-rcu] Make rcutorture more vicious: make quiescent rcutorture less power-hungry Paul E. McKenney
2008-06-22 20:17     ` Arjan van de Ven
2008-06-22 21:02       ` Paul E. McKenney
2008-06-24 11:37         ` Ingo Molnar
2008-06-23 17:54       ` Darren Hart
2008-06-23 18:07         ` Arjan van de Ven
2008-06-23 20:02           ` Darren Hart
2008-06-23 20:07             ` Arjan van de Ven
2008-06-23 20:15             ` Paul E. McKenney
2008-06-23 21:28               ` Darren Hart
2008-06-22 20:58     ` Vegard Nossum
2008-06-22 21:24       ` Vegard Nossum
2008-06-25 19:24     ` [PATCH -tip-rcu] Make rcutorture more vicious: invoke RCU readers from irq handlers (timers) Paul E. McKenney
2008-06-26  7:22       ` Ingo Molnar
2008-06-26 15:48         ` 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=20080619092914.GB15228@elte.hu \
    --to=mingo@elte.hu \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=dino@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=josh@freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niv@us.ibm.com \
    --cc=oleg@tv-sign.ru \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    --cc=vegard.nossum@gmail.com \
    /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

all inboxes | Powered by JetHome®