From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Voyager subarchitecture for 2.5.46
Date: 6 Nov 2002 14:36:32 -0800 [thread overview]
Message-ID: <aqc5hg$ugp$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211060729210.2393-100000@home.transmeta.com
Followup to: <Pine.LNX.4.44.0211060729210.2393-100000@home.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.kernel
>
> I disagree.
>
> We should use the TSC everywhere (if it exists, of course), and the fact
> that two CPU's don't run synchronized shouldn't matter.
>
If it exists, and works :-/
> It's clearly stupid in the long run to depend on the TSC synchronization.
> We should consider different CPU's to be different clock-domains, and just
> synchronize them using the primitives we already have (hey, people can use
> ntp to synchronize over networks quite well, and that's without the kind
> of synchronization primitives that we have within the same box).
Synchronizing them is nice, since it makes RDTSC usable in user
space (without nodelocking.) If it ain't doable, then it ain't.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-11-06 22:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 20:45 Voyager subarchitecture for 2.5.46 J.E.J. Bottomley
2002-11-06 2:31 ` john stultz
2002-11-06 13:43 ` Alan Cox
2002-11-06 21:35 ` john stultz
2002-11-06 15:03 ` J.E.J. Bottomley
2002-11-06 15:38 ` Alan Cox
2002-11-06 16:09 ` Christer Weinigel
2002-11-06 15:45 ` Linus Torvalds
2002-11-06 16:19 ` Alan Cox
2002-11-06 16:12 ` Linus Torvalds
2002-11-06 16:45 ` Alan Cox
2002-11-10 16:30 ` Pavel Machek
2002-11-10 18:59 ` Linus Torvalds
2002-11-10 19:18 ` Pavel Machek
2002-11-10 19:31 ` Linus Torvalds
2002-11-10 19:42 ` Pavel Machek
2002-11-10 19:48 ` Vojtech Pavlik
2002-11-10 20:02 ` Sean Neakums
2002-11-10 20:16 ` Lars Marowsky-Bree
2002-11-10 22:11 ` Alan Cox
2002-11-10 19:46 ` Vojtech Pavlik
2002-11-11 20:40 ` john stultz
2002-11-11 20:57 ` J.E.J. Bottomley
2002-11-11 21:36 ` William Lee Irwin III
2002-11-11 21:58 ` john stultz
2002-11-11 22:49 ` J.E.J. Bottomley
2002-11-11 23:12 ` john stultz
2002-11-12 12:16 ` Pavel Machek
2002-11-11 22:08 ` Vojtech Pavlik
2002-11-06 20:07 ` john stultz
2002-11-06 22:36 ` H. Peter Anvin [this message]
2002-11-06 19:30 ` john stultz
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='aqc5hg$ugp$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@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