From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, dipankar@in.ibm.com,
rostedt@goodmis.org, bhuey@lnxw.com, shemminger@osdl.org,
rusty@au1.ibm.com
Subject: Re: [RFC,PATCH] RCU and CONFIG_PREEMPT_RT sane patch
Date: Thu, 4 Aug 2005 07:49:33 -0700 [thread overview]
Message-ID: <20050804144933.GB1297@us.ibm.com> (raw)
In-Reply-To: <20050804141527.GA15447@elte.hu>
On Thu, Aug 04, 2005 at 04:15:27PM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@us.ibm.com> wrote:
>
> > Hello!
> >
> > The attached patch passes 20 hours of the internal-to-RCU torture test
> > (see the code in the attached patch under CONFIG_RCU_TORTURE_TEST),
> > which is a good improvement over last week's version, which would fail
> > this test in less than two seconds -- this despite passing kernbench
> > with flying colors and passing LTP 90% of the time. Sometimes there
> > is no substitute for a good in-kernel stress test...
> >
> > The attached version of the patch seems to me to be ready for a larger
> > audience.
>
> Cool! I've merged your patch to the -52-12 version of the -RT patch. You
> can get it from the usual place:
>
> http://redhat.com/~mingo/realtime-preempt/
>
> also, i've attached a port against 2.6.13-rc4. I have done this because
> the PREEMPT_RCU patch in my tree is applied before the core-PREEMPT_RT
> patch. I have fixed up the CONFIG_PREEMPT compilation branch and have
> removed your #error define - it built and booted fine on an UP box but
> there are no guarantees ...
Sounds great!!! I will give it a thorough hammering in both the
CONFIG_PREEMPT and CONFIG_PREEMPT_RT environments.
Thanx, Paul
next prev parent reply other threads:[~2005-08-04 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 17:11 [RFC,PATCH] RCU and CONFIG_PREEMPT_RT sane patch Paul E. McKenney
2005-08-04 14:15 ` Ingo Molnar
2005-08-04 14:49 ` Paul E. McKenney [this message]
2005-08-04 16:50 ` 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=20050804144933.GB1297@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=bhuey@lnxw.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=rusty@au1.ibm.com \
--cc=shemminger@osdl.org \
/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