From: Greg KH <gregkh@linuxfoundation.org>
To: stefani@seibold.net
Cc: linux-kernel@vger.kernel.org
Subject: VDSO support for 32bit time functions
Date: Mon, 20 Jan 2014 23:51:23 -0800 [thread overview]
Message-ID: <20140121075123.GA32170@kroah.com> (raw)
Hi Stefani,
About a year ago you posted a big patch to implement VDSO support for
32bit functions, and the response was a request to clean it up a bit by
breaking up the generic bits into a series to make it easier to review /
apply.
The patch I'm referring to can be found here:
http://thread.gmane.org/gmane.linux.kernel/1411713
Did that ever happen?
If not, any specific reason why? Do you have a newer version somewhere
for "modern" kernel versions?
If you're not interested in this anymore, mind if I take it up based on
your last version?
I'm getting some complaints that this type of thing would really be good
as 32bit gettimeofday() on 64bit kernels is really slow (65 nanoseconds
on 32bit vs. 17 nanoseconds on 64bit on a high-end i7 processor.)
thanks,
greg k-h
next reply other threads:[~2014-01-21 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 7:51 Greg KH [this message]
2014-01-21 20:54 ` VDSO support for 32bit time functions Stefani Seibold
2014-01-22 1:34 ` Greg KH
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=20140121075123.GA32170@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefani@seibold.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