R
Rmyers1400
Subject: Re: Intel COO signals willingness to go with AMD64!!
You are trying to turn one argument into two separate arguments to obscure the
fact that the way that you as an engineer who has supposedly seen and done it
all wants to remember history doesn't correspond to reality.
about cache and they were still worried about the memory wall because of these
things called obligatory cache misses. Now I know that none of these people
were probably real engineers because they didn't work on what you regard as
real computers. Nevertheless, they wrote papers and managed to get them
published in refereed journals. I'm sure that if only their had been a real
(mainframe) engineer in their midst, he or she could have straightened things
out for those poor, misguided slobs, but history didn't go down that way. They
knew about all the tricks you mentioned, and they still expected execution time
to be dominated by first reference misses.
execution resources is not a big contributor as far as I know. If that were
the big issue, it would be a very easy problem to fix.
Pipelines get stalled because of branch mispredicts and because of cache misses
that can't be hidden. Branch misprediction really is a separate issue. The
primary technique for hiding so-called compulstory misses is...OoO.
tiresome brand of engineer that I generally try to avoid if I can help it. I
don't even know why I tried.
to have figured out well ahead of the 1996 paper that OoO wouldn't be a big
help with OLTP.
The real reason they didn't figure it out is because, prior to the nineties, no
one, including mainframe manufacturers, could imagine throwing the number of
transistors at the problem that is necessary to make OoO really work.
"Everything has already been thought of" probably is true in your case, so you
should probably go on believing that it's true for everybody. Life will be
more emotionally satisfying for you that way.
RM
From: Keith R. Williams (e-mail address removed)
Date: 2/8/2004 12:28 PM Eastern Standard Time
Message-id: <[email protected]>
Ah, we shouldn't be using one argument to obfuscate another than,
eh?
You are trying to turn one argument into two separate arguments to obscure the
fact that the way that you as an engineer who has supposedly seen and done it
all wants to remember history doesn't correspond to reality.
Did you *read* my post or the reference it contained? Circa 1994 people _knew_Nope.
Problem: Memory wall (latency)
Solution: Caches (many of 'em), Branch prediction, speculative
execution, speculative loads, swamp with bandwidth, pray.
about cache and they were still worried about the memory wall because of these
things called obligatory cache misses. Now I know that none of these people
were probably real engineers because they didn't work on what you regard as
real computers. Nevertheless, they wrote papers and managed to get them
published in refereed journals. I'm sure that if only their had been a real
(mainframe) engineer in their midst, he or she could have straightened things
out for those poor, misguided slobs, but history didn't go down that way. They
knew about all the tricks you mentioned, and they still expected execution time
to be dominated by first reference misses.
And what is it, exactly, that you think causes pipeline stalls? Contention forProblem: How to reduce pipeline stalls
Solution: OoO
execution resources is not a big contributor as far as I know. If that were
the big issue, it would be a very easy problem to fix.
Pipelines get stalled because of branch mispredicts and because of cache misses
that can't be hidden. Branch misprediction really is a separate issue. The
primary technique for hiding so-called compulstory misses is...OoO.
The only existence theorem I see being proved here is of a particularlyThe "existence theorem" is in my favor. It was, thus that is the
way it is.
tiresome brand of engineer that I generally try to avoid if I can help it. I
don't even know why I tried.
Transaction processing doesn't have to be *all* that mainframes do for peopleTP is all mainframes do? I don't *think* so. When you're theory
starts out with a false premiss it's time to junk the theory.
to have figured out well ahead of the 1996 paper that OoO wouldn't be a big
help with OLTP.
The real reason they didn't figure it out is because, prior to the nineties, no
one, including mainframe manufacturers, could imagine throwing the number of
transistors at the problem that is necessary to make OoO really work.
"Everything has already been thought of" probably is true in your case, so you
should probably go on believing that it's true for everybody. Life will be
more emotionally satisfying for you that way.
RM