On Wed, Nov 16, 2005 at 09:40:37AM +0100, Ingo Molnar wrote:
>
> * K.R. Foley <[email protected]> wrote:
>
> > > - big RCU torture-test update (Paul E. McKenney)
> >
> > In case anyone else makes the same mistake I did. If you are using the
> > same config from a previous build, you may have RCU_TORTURE_TEST=Y
> > (not module) and not even know it when running RT patches. You will
> > however definitely notice it if you use the config to build a non RT
> > kernel like 2.6.15-rc1. The previous RT patch defaulted
> > RCU_TORTURE_TEST=y. By the way, the fact that I didn't even notice
> > that the torture test was running with the RT kernel is a true measure
> > of how well things have progressed. :-)
>
> yeah - i left it on by default, i usually do that with new debugging
> features, to give new code more exposure. In other words, mass
> distributed RCU stress-testing by stealth ;-)
Cool!!! If anyone sees a printk line starting with "rcutorture:"
that includes the string "!!!", please pass it along accompanied by
your config and what your workload was doing at the time.
Thanx, Paul
> I'll make it default-off once the RCU related changes have calmed down.
> The rcutorture kernel threads run at nice +19 so they should be barely
> noticeable. (except for a sudden and unexplained spike in the world's
> power consumption, and the resulting energy crisis ;-)
>
> Ingo
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
