From: Rusty Russell <rusty@rustcorp.com.au>
To: Tejun Heo <tj@kernel.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Kent Overstreet <koverstreet@google.com>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: A question on RCU vs. preempt-RCU
Date: Tue, 18 Jun 2013 14:51:13 +0930 [thread overview]
Message-ID: <87obb4ngdy.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20130617182023.GH32663@mtj.dyndns.org>
Tejun Heo <tj@kernel.org> writes:
> Buth yeah, interesting trick. We'll be doing IPIs, flushing TLB and
> taking faults until it hits zero. It'll all depend on the frequency
> of preemption but given that branches don't tend to be too expensive
> on modern processors, maybe it'd be a bit too hairy for possibly
> marginal gain?
Yeah, I'm not convinced either, but I am hoping some enthusiast will run
with the idea in hope of Fame and Glory :)
Cheers,
Rusty.
next prev parent reply other threads:[~2013-06-18 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 2:36 A question on RCU vs. preempt-RCU Tejun Heo
2013-06-16 6:46 ` Rusty Russell
2013-06-17 18:20 ` Tejun Heo
2013-06-18 5:21 ` Rusty Russell [this message]
2013-06-20 3:23 ` Steven Rostedt
2013-06-16 14:13 ` Paul E. McKenney
2013-06-16 21:40 ` Tejun Heo
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=87obb4ngdy.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=koverstreet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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