All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Sivaraj <santosh@fossix.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v6] powerpc/vdso64: Add support for CLOCK_{REALTIME/MONOTONIC}_COARSE
Date: Wed, 11 Oct 2017 13:08:13 +0530	[thread overview]
Message-ID: <20171011073813.uzmxrhwxprs5awzj@santosiv.in.ibm.com> (raw)
In-Reply-To: <20171011070443.5lupjenfs4ycwd5q@naverao1-tp.localdomain>

* Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com> wrote (on 2017-10-11 07:04:43 +0000):

> Hi Santosh,
> This seems to have gone from v4 to v6 -- did I miss v5?

Nope, this is indeed v5, a typo :-(
>
> On 2017/10/10 11:10PM, Santosh Sivaraj wrote:
> > Current vDSO64 implementation does not have support for coarse clocks
> > (CLOCK_MONOTONIC_COARSE, CLOCK_REALTIME_COARSE), for which it falls back
> > to system call, increasing the response time, vDSO implementation reduces
> > the cycle time. Below is a benchmark of the difference in execution times.
> > 
> > (Non-coarse clocks are also included just for completion)
> > 
> > clock-gettime-realtime: syscall: 172 nsec/call
> > clock-gettime-realtime:    libc: 28 nsec/call
> > clock-gettime-realtime:    vdso: 22 nsec/call
> > clock-gettime-monotonic: syscall: 171 nsec/call
> > clock-gettime-monotonic:    libc: 30 nsec/call
> > clock-gettime-monotonic:    vdso: 25 nsec/call
> > clock-gettime-realtime-coarse: syscall: 153 nsec/call
> > clock-gettime-realtime-coarse:    libc: 16 nsec/call
> > clock-gettime-realtime-coarse:    vdso: 10 nsec/call
> > clock-gettime-monotonic-coarse: syscall: 167 nsec/call
> > clock-gettime-monotonic-coarse:    libc: 17 nsec/call
> > clock-gettime-monotonic-coarse:    vdso: 11 nsec/call
> > 
> > CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > Signed-off-by: Santosh Sivaraj <santosh@fossix.org>
> > ---
> >  arch/powerpc/kernel/asm-offsets.c         |  2 +
> >  arch/powerpc/kernel/vdso64/gettimeofday.S | 67 ++++++++++++++++++++++++++-----
> >  2 files changed, 58 insertions(+), 11 deletions(-)
> 
> ... and no changes since the last rev?

There is that one line change of label. But otherwise its the same.
> 
> It is better to post new versions in a separate thread and to include 
> the changelog for easier review.
>

Sure.

Thanks,
Santosh
> 
> - Naveen
> 

-- 

  reply	other threads:[~2017-10-11  7:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18  9:23 [PATCH 1/2] powerpc/vdso64: Coarse timer support preparatory patch Santosh Sivaraj
2017-09-18  9:23 ` [PATCH 2/2] powerpc/vdso64: Add support for CLOCK_{REALTIME/MONOTONIC}_COARSE Santosh Sivaraj
2017-10-06  9:28   ` Naveen N. Rao
2017-10-09  6:27     ` Santosh Sivaraj
2017-10-06 11:25   ` Naveen N. Rao
2017-10-09  6:23     ` Santosh Sivaraj
2017-10-09  8:09     ` [PATCH v4] " Santosh Sivaraj
2017-10-09 10:39       ` Naveen N. Rao
2017-10-10  9:03         ` Santosh Sivaraj
2017-10-10  9:30           ` Naveen N. Rao
2017-10-10 23:10             ` [PATCH v6] " Santosh Sivaraj
2017-10-11  7:04               ` Naveen N. Rao
2017-10-11  7:38                 ` Santosh Sivaraj [this message]
2017-10-06  9:03 ` [PATCH 1/2] powerpc/vdso64: Coarse timer support preparatory patch Naveen N. Rao
2017-10-06 10:13   ` Michael Ellerman
2017-10-16  5:49 [PATCH v6] powerpc/vdso64: Add support for CLOCK_{REALTIME/MONOTONIC}_COARSE Santosh Sivaraj

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=20171011073813.uzmxrhwxprs5awzj@santosiv.in.ibm.com \
    --to=santosh@fossix.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    /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.