From: Geoff Levand <geoffrey.levand@am.sony.com>
To: randy_dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, george@mvista.com
Subject: Re: [PATCH] Fix posix_bump_timer args
Date: Wed, 06 Jul 2005 17:40:20 -0700 [thread overview]
Message-ID: <42CC79F4.5010605@am.sony.com> (raw)
In-Reply-To: <20050706171756.258d4f33.rdunlap@xenotime.net>
randy_dunlap wrote:
> On Wed, 06 Jul 2005 11:26:31 -0700 Geoff Levand wrote:
>
> | This patch makes posix_bump_timer() consistent with common convention
> | by expecting a pointer to the structure be passed.
> |
> | Please apply.
>
> Does it matter other than for consistency?
>
> E.g., in a large system with thousands of timers, it seems that it
> could (at least theoretically) have a negative impact by using a
> pointer dereference instead of a known fixed address.
> or am I just imagining that?
>
I pulled this out of the HRT patches. In general it was agreed that
the change is for the best.
-Geoff
prev parent reply other threads:[~2005-07-07 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 18:26 [PATCH] Fix posix_bump_timer args Geoff Levand
2005-07-07 0:17 ` randy_dunlap
2005-07-07 0:40 ` Geoff Levand [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=42CC79F4.5010605@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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