From: Michael Ellerman <michael@ellerman.id.au>
To: Adhemerval Zanella <azanella@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] [RFC] powerpc: Add VDSO version of time
Date: Thu, 18 Apr 2013 15:58:42 +1000 [thread overview]
Message-ID: <20130418055842.GA14456@concordia> (raw)
In-Reply-To: <5162CEBE.1020607@linux.vnet.ibm.com>
On Mon, Apr 08, 2013 at 11:05:50AM -0300, Adhemerval Zanella wrote:
> On 04/05/2013 03:21 AM, Michael Ellerman wrote:
> > On Tue, Mar 19, 2013 at 04:55:31PM -0300, Adhemerval Zanella wrote:
> >> Hi all,
> >>
> >> This patch implement the time syscall as vDSO. I have a glibc patch
> >> to use it as IFUNC (as latest gettimeofday patch). Below the perf
> >> numbers:
> >>
> >> Baseline PPC32: 380 nsec
> >> Baseline PPC64: 352 nsec
> >> vdso PPC32: 20 nsec
> >> vdso PPC64: 20 nsec
> >>
> >> I focused on 64 bit kernel, do I need to provide a scheme for 32 bits
> >> as well?
> > You did provide a 32-bit implementation. I take it you haven't tested
> > that though? Can you test it?
>
> Hi,
>
> I didn't build a 32 bit kernel, but I tested 32 bits binaries (that uses
> the VDSO32 implantation) without any issue. Performance gains are similar.
OK. Please send an updated version of the patch which a changelog
describing the testing you've done, and add your Signed-off-by to the
patch.
cheers
next prev parent reply other threads:[~2013-04-18 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 19:55 [PATCH] [RFC] powerpc: Add VDSO version of time Adhemerval Zanella
2013-03-20 5:00 ` Benjamin Herrenschmidt
2013-03-21 13:40 ` Adhemerval Zanella
2013-03-26 17:32 ` Adhemerval Zanella
2013-04-04 19:22 ` Adhemerval Zanella
2013-04-05 6:21 ` Michael Ellerman
2013-04-05 18:49 ` Adhemerval Zanella
2013-04-08 14:05 ` Adhemerval Zanella
2013-04-18 5:58 ` Michael Ellerman [this message]
2013-04-18 22:38 ` Anton Blanchard
2013-04-22 19:29 ` Adhemerval Zanella
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=20130418055842.GA14456@concordia \
--to=michael@ellerman.id.au \
--cc=azanella@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).