From: Badari Pulavarty <pbadari@gmail.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: paulmck@us.ibm.com, Andrew Morton <akpm@osdl.org>,
Ingo Oeser <ioe-lkml@rameria.de>,
lkml <linux-kernel@vger.kernel.org>,
arjan@infradead.org, pavel@ucw.cz, dipankar@in.ibm.com,
vatsa@in.ibm.com, rusty@au1.ib.com, mingo@elte.hu,
manfred@colorfullife.com, gregkh@kroah.com
Subject: Re: [PATCH] RCU torture-testing kernel module
Date: Mon, 24 Oct 2005 11:10:58 -0700 [thread overview]
Message-ID: <1130177458.6831.11.camel@localhost.localdomain> (raw)
In-Reply-To: <5D5AD6EA-5D6E-47DA-8170-0729F9C32889@mac.com>
On Mon, 2005-10-24 at 13:59 -0400, Kyle Moffett wrote:
> On Oct 24, 2005, at 12:24:33, Badari Pulavarty wrote:
> > Paul,
> >
> > I enabled RCU_TORTURE_TEST in 2.6.14-rc5-mm1. My machine took 10+
> > minutes to boot and let me login. RCU kthreads are hogging the
> > CPU. Is this expected ?
>
> Uhh... It's a torture test. What exactly do _you_ expect it will
> do? I think the idea is to enable it as a module and load it when
> you want to start torture testing, and unload it when done.
> "TORTURE_TEST"s are not for production systems :-D.
I was expecting that - even if its compiled in, there would be
a way to turn on/off the tests from /proc or something :)
Thanks,
Badari
next prev parent reply other threads:[~2005-10-24 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 23:12 [PATCH] RCU torture-testing kernel module Paul E. McKenney
2005-10-23 7:22 ` Ingo Oeser
2005-10-23 14:36 ` Paul E. McKenney
2005-10-23 18:55 ` Ingo Oeser
2005-10-23 19:05 ` Andrew Morton
2005-10-24 0:47 ` Paul E. McKenney
2005-10-24 14:59 ` Ingo Oeser
2005-10-24 16:24 ` Badari Pulavarty
2005-10-24 17:59 ` Kyle Moffett
2005-10-24 18:10 ` Badari Pulavarty [this message]
2005-10-24 22:29 ` Kyle Moffett
2005-10-24 23:03 ` Paul E. McKenney
2005-10-24 22:54 ` Paul E. McKenney
2005-10-24 23:09 ` Badari Pulavarty
2005-10-23 19:47 ` Greg KH
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=1130177458.6831.11.camel@localhost.localdomain \
--to=pbadari@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=dipankar@in.ibm.com \
--cc=gregkh@kroah.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
--cc=mrmacman_g4@mac.com \
--cc=paulmck@us.ibm.com \
--cc=pavel@ucw.cz \
--cc=rusty@au1.ib.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox