Messages in this thread | | | Subject | Re: AMD X2 unsynced TSC fix? | From | Lee Revell <> | Date | Sat, 28 Oct 2006 14:08:34 -0400 |
| |
On Sat, 2006-10-28 at 07:28 +0200, Willy Tarreau wrote: > On Fri, Oct 27, 2006 at 11:28:00PM -0400, Lee Revell wrote: > > On Fri, 2006-10-27 at 18:04 -0700, Andi Kleen wrote: > > > I don't think it makes too much sense to hack on pure RDTSC when > > > gtod is fast enough -- RDTSC will be always icky and hard to use. > > > > I agree FWIW, our application would be happy to just use gtod if it > > wasn't so slow on these machines. > > Agreed, I had to turn about 20 dual-core servers to single core because > the only way to get a monotonic gtod made it so slow that it was not > worth using a dual-core. I initially considered buying one dual-core > AMD for my own use, but after seeing this, I'm definitely sure I won't > ever buy one as long as this problem is not fixed, as it causes too > many problems.
Does anyone know if the problem will really be fixed in new CPUs, as AMD promised a year or so ago?
http://lkml.org/lkml/2005/11/4/173
Since that post, there has been Socket F and AM2 which apparently have the same issue.
Were the AMD guys just blowing smoke?
Lee
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |