From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, akpm@osdl.org, dipankar@in.ibm.com,
vatsa@in.ibm.com, rusty@au1.ibm.com, mingo@elte.hu,
manfred@colorfullife.com
Subject: Re: [PATCH] RCU torture testing
Date: Mon, 3 Oct 2005 08:49:39 -0700 [thread overview]
Message-ID: <20051003154939.GF1300@us.ibm.com> (raw)
In-Reply-To: <1128353520.17024.19.camel@laptopd505.fenrus.org>
On Mon, Oct 03, 2005 at 05:31:59PM +0200, Arjan van de Ven wrote:
>
> > Good point -- all I really need for module parameters is the number
> > of readers. I should be able to have module load start the test and
> > module unload stop it (any problems with this approach?).
>
> only one potential gotcha; it means you can't load the system to the
> extend that the shell doesn't get cpu time otherwise the admin can never
> issue the unload. Maybe a time limit on the testing? (optional as module
> parm for all I care)
Makes sense to me! Not an issue for the RCU torture test, but it certainly
might be for other tests.
Thanx, Paul
next prev parent reply other threads:[~2005-10-03 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 18:20 [PATCH] RCU torture testing Paul E. McKenney
2005-10-02 0:11 ` Greg KH
2005-10-03 14:28 ` Paul E. McKenney
2005-10-03 14:48 ` Greg KH
2005-10-02 21:05 ` Pavel Machek
2005-10-03 6:30 ` Ingo Molnar
2005-10-03 14:30 ` Paul E. McKenney
2005-10-03 14:36 ` Arjan van de Ven
2005-10-03 15:26 ` Paul E. McKenney
2005-10-03 15:31 ` Arjan van de Ven
2005-10-03 15:49 ` Paul E. McKenney [this message]
2005-10-22 23:09 ` 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=20051003154939.GF1300@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rusty@au1.ibm.com \
--cc=vatsa@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.