From: Steven Rostedt <rostedt@goodmis.org>
To: pavel@pavlinux.ru
Cc: linux-kernel@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
John Kacur <jkacur@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [PATCH RT 0/3] Linux 3.2.57-rt84-rc1
Date: Mon, 28 Apr 2014 09:39:56 -0400 [thread overview]
Message-ID: <20140428093956.78d0f3ea@gandalf.local.home> (raw)
In-Reply-To: <535D8180.1020607@pavlinux.ru>
On Mon, 28 Apr 2014 02:15:28 +0400
Pavel Vasilyev <pavel@pavlinux.ru> wrote:
> 27.04.2014 18:39, Steven Rostedt пишет:
> > Dear RT Folks,
> >
> > This is the RT stable review cycle of patch 3.2.57-rt84-rc1.
> >
> > Please scream at me if I messed something up. Please test the patches too.
>
>
> More than two years our thin clients (about 5000 machines, Intel Atom, x86_32)
> work with RCU_BOOST.
>
> CONFIG_RCU_BOOST=y
> CONFIG_RCU_BOOST_PRIO=80
> CONFIG_RCU_BOOST_DELAY=400
>
Is this just a confirmation of having RCU_BOOST default y for
PREEMPT_RT is a good thing?
Thanks,
-- Steve
next prev parent reply other threads:[~2014-04-28 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 14:39 [PATCH RT 0/3] Linux 3.2.57-rt84-rc1 Steven Rostedt
2014-04-27 14:39 ` [PATCH RT 1/3] net: gianfar: do not disable interrupts Steven Rostedt
2014-04-27 14:39 ` [PATCH RT 2/3] rcu: make RCU_BOOST default on RT Steven Rostedt
2014-04-27 14:39 ` [PATCH RT 3/3] Linux 3.2.57-rt84-rc1 Steven Rostedt
2014-04-27 22:15 ` [PATCH RT 0/3] " Pavel Vasilyev
2014-04-28 13:39 ` Steven Rostedt [this message]
2014-04-29 15:48 ` Pavel Vasilyev
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=20140428093956.78d0f3ea@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=pavel@pavlinux.ru \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).