From: Badari Pulavarty <pbadari@gmail.com>
To: paulmck@us.ibm.com
Cc: 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 09:24:33 -0700 [thread overview]
Message-ID: <1130171073.6831.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20051024004709.GA9454@us.ibm.com>
On Sun, 2005-10-23 at 17:47 -0700, Paul E. McKenney wrote:
> On Sun, Oct 23, 2005 at 12:05:21PM -0700, Andrew Morton wrote:
> > Ingo Oeser <ioe-lkml@rameria.de> wrote:
> > >
> > > DEBUG_KERNEL should do nothing more than showing the debugging
> > > options.
> >
> > yup.
> >
> > > E.g. I don't expect to enable any additional code in an
> > > unrelated file, if I enable Magic-SysRQ on an embedded, unattended device
> > > to be able to analyze potential problems via serial console.
> > >
> > > @Andrew: Would you accept a patch to fix that?
> >
> > more yup.
>
> OK, the attached patch covers this and also fixes the redundant #include
> that Greg KH spotted.
>
> Thoughts?
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 ?
Thanks,
Badari
top - 15:32:55 up 22 min, 1 user, load average: 10.96, 12.07, 9.18
Tasks: 94 total, 11 running, 83 sleeping, 0 stopped, 0 zombie
Cpu(s): 2.5% us, 97.5% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi,
0.0% si
Mem: 7145152k total, 350656k used, 6794496k free, 50876k buffers
Swap: 1048784k total, 0k used, 1048784k free, 160168k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
168 root 20 -5 0 0 0 R 50.2 0.0 10:44.01
rcu_torture_rea
171 root 20 -5 0 0 0 R 50.2 0.0 10:47.86
rcu_torture_rea
175 root 20 -5 0 0 0 R 50.2 0.0 10:49.83
rcu_torture_rea
169 root 20 -5 0 0 0 R 49.9 0.0 10:47.07
rcu_torture_rea
172 root 20 -5 0 0 0 R 49.9 0.0 10:50.04
rcu_torture_rea
173 root 20 -5 0 0 0 R 49.9 0.0 10:43.79
rcu_torture_rea
174 root 20 -5 0 0 0 R 49.9 0.0 10:39.16
rcu_torture_rea
170 root 20 -5 0 0 0 R 40.2 0.0 10:38.68
rcu_torture_rea
next prev parent reply other threads:[~2005-10-24 16:25 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 [this message]
2005-10-24 17:59 ` Kyle Moffett
2005-10-24 18:10 ` Badari Pulavarty
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=1130171073.6831.6.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=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