From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, dipankar@in.ibm.com
Subject: Re: [RFC] RCU and CONFIG_PREEMPT_RT progress, part 2
Date: Mon, 11 Jul 2005 17:16:27 +0200 [thread overview]
Message-ID: <20050711151627.GA19794@elte.hu> (raw)
In-Reply-To: <20050711150728.GA1497@us.ibm.com>
* Paul E. McKenney <paulmck@us.ibm.com> wrote:
> Hello!
>
> More progress on CONFIG_PREEMPT_RT-compatible RCU.
>
> o Continued prototyping Linux-kernel implementation, still
> in the CONFIG_PREEMPT environment.
cool! With the debugging code removed it doesnt look all that complex.
Do you think i can attempt to plug this into the -RT tree, or should i
wait some more? (One observation: if you know some branch is slowpath in
a common codepath then it's useful to mark the condition via unlikely().
That results in better code layout and is also a guidance for the casual
reader of the code.)
Ingo
next prev parent reply other threads:[~2005-07-11 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 1:38 [RFC] RCU and CONFIG_PREEMPT_RT progress, part 2 Paul E. McKenney
2005-07-11 15:07 ` Paul E. McKenney
2005-07-11 15:16 ` Ingo Molnar [this message]
2005-07-11 15:51 ` 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=20050711151627.GA19794@elte.hu \
--to=mingo@elte.hu \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.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;
as well as URLs for NNTP newsgroup(s).