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

Where were you when I was writing this stuff :).  I agree with most all of it, 
save the following:

 >  /*
 > + * Define this to initialize every k_clock function table so all its
 > + * function pointers are non-null, and always do indirect calls through the
 > + * table.  Leave it undefined to instead leave null function pointers and
 > + * decide at the call sites between a direct call (maybe inlined) to the
 > + * default function and an indirect call through the table when it's filled
 > + * in.  Which style is preferable is whichever performs better in the
 > + * common case of using the default functions.

 > +#define CLOCK_DISPATCH_DIRECT

As I understand it modern machines, the indirect call does really bad things to 
the pipeline.  The default call, even preceeded by the if, will be much faster 
by this reasoning.  I would, therefor, prefer not defining CLOCK_DISPATCH_DIRECT.


-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/


  reply	other threads:[~2005-01-25  2: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 [this message]
2005-01-25  2:49   ` Andrew Morton
2005-01-25 23:13     ` Roland McGrath
2005-01-25  4:11   ` Ulrich Drepper

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=41F5ABB8.8070308@mvista.com \
    --to=george@mvista.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=drepper@redhat.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 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.