From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Andrea Arcangeli <andrea@suse.de>,
john stultz <johnstul@us.ibm.com>,
Linus Torvalds <torvalds@transmeta.com>,
Michael Hohnbaum <hbaum@us.ibm.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
george anzinger <george@mvista.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] linux-2.5.34_vsyscall_A0
Date: 21 Oct 2002 14:18:22 +0100 [thread overview]
Message-ID: <1035206302.28189.95.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <1034957619.5401.8.camel@dell_ss3.pdx.osdl.net>
On Fri, 2002-10-18 at 17:13, Stephen Hemminger wrote:
> It would be great to rework the whole TSC time of day stuff to work with
> per cpu data and allow unsychronized TSC's like NUMA. The problem is
> that for fast user level access, there would need to be some way to find
The timer isnt even necessarily constant rate. The tsc is a nice tool
for debugging. Using it as a clock was not in the long run brilliant.
Don't try and continue it further, we have ACPI and HPET and other
better solutions in upcoming PC hardware.
next prev parent reply other threads:[~2002-10-21 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 4:25 john stultz
2002-10-18 4:26 ` [RFC] linux-2.5.34_vsyscall_A0 - Test App john stultz
2002-10-18 11:14 ` [RFC][PATCH] linux-2.5.34_vsyscall_A0 Andrea Arcangeli
2002-10-18 16:13 ` Stephen Hemminger
2002-10-18 16:45 ` george anzinger
2002-10-18 17:11 ` Andrea Arcangeli
2002-10-18 17:19 ` Linus Torvalds
2002-10-18 17:21 ` Andrea Arcangeli
2002-10-18 18:37 ` Stephen Hemminger
2002-10-18 18:51 ` Andrea Arcangeli
2002-10-18 19:30 ` george anzinger
2002-10-18 17:01 ` Andrea Arcangeli
2002-10-21 13:18 ` Alan Cox [this message]
2002-10-21 17:15 ` john stultz
2002-10-18 16:39 ` john stultz
2002-10-18 18:54 ` [RFC] vsyscall_A0 LD_PRELOAD implementation john stultz
2002-10-21 22:44 ` [RFC][PATCH] linux-2.5.34_vsyscall_A0 Stephen Hemminger
2002-10-18 18:21 Manfred Spraul
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=1035206302.28189.95.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=george@mvista.com \
--cc=hbaum@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=shemminger@osdl.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®