public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: george@mvista.com
Cc: Roland McGrath <roland@redhat.com>, Andrew Morton <akpm@osdl.org>,
	Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 1/7] posix-timers: tidy up clock interfaces and consolidate dispatch logic
Date: Mon, 24 Jan 2005 20:11:00 -0800	[thread overview]
Message-ID: <41F5C6D4.4030106@redhat.com> (raw)
In-Reply-To: <41F5ABB8.8070308@mvista.com>

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

George Anzinger wrote:
> As I understand it modern machines, the indirect call does really bad 
> things to the pipeline.

Unless the call happens often, really often, you'll not be able to 
measure differences.  Indirect jump obviously cause pipeline stalls 
which often, but not always, can be avoided with direct calls.  But we 
are not talking here about huge delays.  And the delays are equivalent 
in cost to a mispredicted branch.  If you have a couple of ifs in a row 
you are likely to incur problems with the branch prediction.  I would 
just use the indirect jumps but if you want, do some timing and see 
whether you can filter the difference out of the noise.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

      parent reply	other threads:[~2005-01-25  4:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 23:22 [PATCH 1/7] posix-timers: tidy up clock interfaces and consolidate dispatch logic Roland McGrath
2005-01-25  2:15 ` George Anzinger
2005-01-25  2:49   ` Andrew Morton
2005-01-25 23:13     ` Roland McGrath
2005-01-25  4:11   ` Ulrich Drepper [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=41F5C6D4.4030106@redhat.com \
    --to=drepper@redhat.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=torvalds@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