From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] provide /proc/sal/itc_drift through AUX?
Date: Wed, 19 Mar 2003 21:39:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705273@msgid-missing> (raw)
Hi
I was wondering what people think about providing the information of
/proc/sal/itc_drift as an AUX vector?
The problem is that on some NUMA boxen (such as the SGI boxes), the ITC
isn't synchronized across nodes and we can't rely on ar.itc in userland
for implementing the high-precision timing. I believe the IBM NUMA-Q
team has a similar problem that could be solved in a similar way on
ia32?
Instead one can switch to using gettimeofday() for the timing, which
with the new fast syscalls should be quite pleasant.
I have a patch which implements this for glibc-2.2 (will do 2.3 later),
however what I don't like about it is that one ends up opening and
reading /proc/sal/itc_drift in every single binary executed. To avoid
the overhead of this it seems a good idea to me to provide this
information via an AUX vector.
If anybody is interested in the glibc patch, feel free to grab it from
http://www.wildopensource.com/~jes/glibc/itc-drift-patch.diff
For now it's a test patch, though it does seem to behave as expected.
Thoughts?
Cheers,
Jes
next reply other threads:[~2003-03-19 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 21:39 Jes Sorensen [this message]
2003-03-19 23:54 ` [Linux-ia64] provide /proc/sal/itc_drift through AUX? David Mosberger
2003-03-20 2:06 ` Jes Sorensen
2003-03-20 19:57 ` David Mosberger
2003-03-20 23:55 ` Rich Altmaier
2003-03-21 0:43 ` David Mosberger
2003-03-21 2:04 ` Jes Sorensen
2003-03-21 17:49 ` Jes Sorensen
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=marc-linux-ia64-105590723705273@msgid-missing \
--to=jes@wildopensource.com \
--cc=linux-ia64@vger.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