public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] x86-64: Simplify and speed up vdso clock_gettime
Date: Fri, 23 Mar 2012 16:47:03 -0700	[thread overview]
Message-ID: <4F6D0B77.6070600@linaro.org> (raw)
In-Reply-To: <cover.1332475308.git.luto@amacapital.net>

On 03/22/2012 09:15 PM, Andy Lutomirski wrote:
> I think clock_gettime is already almost as fast as possible, but every
> little bit helps.  Also, I think the diffstat is pretty good for a
> speedup.  Here are some approximate timings.
>
>                               Before       After
> CLOCK_REALTIME                 16.7        15.2
> CLOCK_MONOTONIC                17.3        15.5
> CLOCK_REALTIME_COARSE           3.6         3.0
> CLOCK_MONOTONIC_COARSE          4.2         3.6
>
> These are extracted from an earlier series that's mostly abandoned now [1-2].
> They apply to tip/timers/core commit 57779dc2b3b75bee05ef5d1ada47f615f7a13932.
>
> For the git-inclined, the patches are here:
> https://git.kernel.org/?p=linux/kernel/git/luto/linux.git;a=shortlog;h=refs/heads/timing/vclock_speedup/patch_v1
>
> I'm not sure whether these are 3.4 material.  On the pro side, they've
> technically been floating around since long before the merge window.
> They're also quite straightforward, and they're based on other -tip
> changes (which is why I'm submitting now).  On the con side, they don't
> fix anything, and they're a little later than ideal.

The look straightforward enough. I've queued them at the end of my 3.4 
queue. If Thomas or anyone wants to wait on them, I'll push them off to 3.5

thanks
-john


      parent reply	other threads:[~2012-03-23 23:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  4:15 [PATCH 0/2] x86-64: Simplify and speed up vdso clock_gettime Andy Lutomirski
2012-03-23  4:15 ` [PATCH 1/2] x86-64: Simplify and optimize vdso clock_gettime monotonic variants Andy Lutomirski
2012-03-23  4:15 ` [PATCH 2/2] x86-64: Inline vdso clock_gettime helpers Andy Lutomirski
2012-03-23 23:47 ` John Stultz [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=4F6D0B77.6070600@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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