From: Nicholas Miell <nmiell@comcast.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Chris Snook <chris.snook@gmail.com>,
john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@tglx.de>, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <ak@suse.de>,
nikolag@ca.ibm.com, Darren Hart <dvhltc@us.ibm.com>
Subject: Re: [RFC][PATCH] Introduce CLOCK_REALTIME_COARSE
Date: Sat, 18 Jul 2009 23:48:01 -0700 [thread overview]
Message-ID: <1247986081.9351.21.camel@entropy> (raw)
In-Reply-To: <20090718231429.7ddea95f@infradead.org>
On Sat, 2009-07-18 at 23:14 -0700, Arjan van de Ven wrote:
> it's on x86.. likely/unlikely don't impact the CPU (since there are no
> "ignore the branch predictor" hints), only the code placement.....
But code placement does affect branch prediction (e.g. the Pentium 4
static predictor assumes backward branches are taken, recent AMD
processors prefer you to arrange code such that conditional branches are
not taken, etc.)
--
Nicholas Miell <nmiell@comcast.net>
prev parent reply other threads:[~2009-07-19 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 23:39 [RFC][PATCH] Introduce CLOCK_REALTIME_COARSE john stultz
2009-07-18 8:30 ` Thomas Gleixner
2009-07-18 22:09 ` john stultz
2009-07-18 22:30 ` Arjan van de Ven
2009-07-20 11:17 ` Peter Zijlstra
2009-07-20 12:22 ` Paul E. McKenney
2009-07-20 13:33 ` Arjan van de Ven
2009-07-20 13:49 ` Peter Zijlstra
2009-07-22 21:39 ` Josh Triplett
2009-07-21 22:31 ` john stultz
2009-07-22 1:26 ` john stultz
2009-08-01 12:21 ` Andy Lutomirski
2009-07-18 12:09 ` Ingo Molnar
2009-07-18 22:20 ` john stultz
2009-07-19 3:00 ` Chris Snook
2009-07-19 6:14 ` Arjan van de Ven
2009-07-19 6:48 ` Nicholas Miell [this message]
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=1247986081.9351.21.camel@entropy \
--to=nmiell@comcast.net \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=chris.snook@gmail.com \
--cc=dvhltc@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nikolag@ca.ibm.com \
--cc=tglx@tglx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.