Gaming AMD vs Intel

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

Wes Newell wrote:
*
snip
>
> Serial technologies such as PCI Express and RapidIO require
> serial-deserializer interfaces and have the burden of extensive overhead
> in encoding parallel data into serial data, embedding clock information,
> re-acquiring and decoding the data stream. The parallel technology of
> HyperTransport needs no serdes and clock encoding overhead making it far
> more efficient in data transfers.
>
> I rest my case.;-)
>

The last paragraph you quote, shown above, is Clintonian at best, with
respect to comparing the physical aspects of HT and PCI-E.

--
Del Cecchi
"This post is my own and doesn’t necessarily represent IBM’s positions,
strategies or opinions.”
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Thu, 08 Sep 2005 21:41:36 -0400, Tony Hill wrote:

> On Wed, 07 Sep 2005 16:42:58 -0400, keith <krw@att.bizzzz> wrote:
>>> Too long ago to remember and
>>> I'm too lazy to look it up.🙂 And I just remembered that the Slot A
>>> k7's had it's L2 cache on the cpu board too, and not in the cpu die, but
>>> I don't recall AMD or anyone else using back side bus for it.
>>
>>I'm from Missouri (close, but not really). I never remember a slot-A K7
>>with on-board L2.
>
> There were a *few* Slot-A K7 chips that had integrated L2, but they
> were only released for compatibility purposes (much like what Intel
> did with some of their later Slot-1 PIII chips, though AMD released
> far fewer of such chips). You might even be able to find someone
> still selling such a beast if you look hard enough, just do a search
> for "Thunderbird Slot-A".

I meant the cache on the board (system bus), as opposed to "integrated"
or on the cartridge (on the "back-side").

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Thu, 08 Sep 2005 21:41:35 -0400, Tony Hill wrote:

> On Wed, 07 Sep 2005 05:59:41 GMT, Wes Newell
> <w.newell@TAKEOUTverizon.net> wrote:
>
>>On Tue, 06 Sep 2005 22:18:40 -0400, keith wrote:
>>
>>> On Tue, 06 Sep 2005 19:13:54 +0000, Wes Newell wrote:
>>>
>>>> FSB by definition connects the CPU to the chipset.
>>>
>>> Nope. As George stated, it was in opposition the "back-side <cache> bus"
>>> of the P6. The P5 had no "FSB".
>>>
>>Under your definition of FSB, then no AMD CPU's have ever had a FSB. Let's
>>see just how many people you can convince of that.🙂
>
> Not true at all. The original AMD Athlon had both a front-side bus,
> connecting the CPU to the chipset, I/O and memory, and a backside bus
> that connected the CPU to the cache chips on the Slot-A cartridge.
> This was actually the last x86 CPU that I'm aware of which did have a
> frontside bus (Intel had already gone to integrated cache by this
> time).

Just because the cache is integrated doesn't mean the cache isn't on the
"back side" of the processor. The "back-side" concept was really a
separation of the cache from the memory busses.

> Of course, the EV6 bus used to connect Athlon CPUs to their chipsets is
> only kinda-sorta a bus in itself. Really it's more of a point-to-point
> link, though it's in that fuzzy area that blurs the lines between the
> two a bit (where the GTL+ bus used in the P6 is definitely a bus and
> Hypertransport is definitely not a bus, EV6 falls somewhere in between).

Works for me.

>>While the term may have originated the way you say, it was then later
>>used to indicate the connection between the CPU and the chipset.
>
> Yes, a lot of people incorrectly refer to the a connection between the
> CPU and the chipset as a "Front Side Bus". Just because lots of people
> make a mistake that doesn't mean that they are right.

Yep! It ignores the reason it was called the "front-side bus" to begin
with.

> People also still call the memory controller the "northbridge" and the
> I/O chip a "southbridge", which also makes no sense given that they are
> no longer being connected via PCI and they usually aren't bridges at
> all. Again, just because people incorrectly use a term doesn't make it
> correct.

As long as there is an off-chip memory controller and high-speed
peripherals on the "bridge", it's proper to call it a "north-bridge". If
there is a low-spped bridge hanging off that, "south-bridge" is a useful
concept.

>> Now, that same
>>connection is the HT link of the K8. So it only makes sense to use the
>>same terminology for the very specific connection even though memory
>>data now has own single use bus for the memory.
>
> It doesn't make any sense with the AthlonXP or the P4 and it makes MUCH
> less sense with the Athlon64/Opteron. Just because it's a common
> mistake doesn't make it any less of a mistake.

Why doesn't "front-side bus" work with the P4 or K7? The cache is still
on the "back side" of the processor, even though it's on the chip.

<snip>

>> They function fully indepentant of other buses. If I assume you
>>are talking about the HT link used to connect the K8 cpu's to the
>>chipset, I'd just answer that it's in the same place as back side of the
>>K7 CPU's FSB. You're really digging a hole for yourself here.
>
> The original Athlon had a backside bus with to the cache chips on the
> cartridge. This was later removed with the "Thunderbird" chips with
> integrated cache. As such, from the "Thunderbird" on forward (including
> all AthlonXP chips) there was no FSB on the AthlonXP. Same goes for the
> PIII from the "Coppermine" onwards as well as ALL P4 chips. None of
> those have FSBs, despite the fact that many people incorrectly use the
> term to describe the system bus of said chips.

No, the back side bus wasn't removed. It was integrated onto the chip.
The architecture is the same, if the parts moved around.

>>>> IOW's using the term FSB
>>>> specifically refers to the connection between the CPU and chipset,
>>>
>>> No, it doesn't. I specifically refers to the fact that the caches are
>>> on the other side (back side) of the P6 memory bus. That architecture
>>> was around for a while, so it stuck. There was no "FSB" in the P5
>>> architecture. It's an invention of the P6 and should stay there,
>>> since it no longer describes any function.
>>>
>>Why are you stuck on the Pentium Pro. FSB has been used for years to
>>indicate the connection between the CPU and the chipset.
>
> The term "Front Side Bus" was never used with the Pentium chips because
> there was only one bus. FSB came into computer use with the PentiumPro
> where Intel introduced a chip with a Frontside Bus (connecting to main
> memory and I/O) and a Backside bus (connecting to cache). The
> terminology continued through the PII and early PIII chips, as well as
> early Athlon chips, as they had two buses, one for memory and I/O and
> the other for cache. For chips with only a single bus the term "FSB"
> makes no sense. Never has and never will, no matter how many people
> make such a mistake.

I dissagree. The back-side bus was integrated onto the chip. Again, the
memory architecture was the same.

> With the Athlon64 and Opteron it's just more obviously incorrect than it
> is with the AthlonXP and P4 chips.

It *is* incorrect, not so with the P4 or K7.

>>>> while
>>>> using the term HT link could be any of many different type of
>>>> connections an HT link is used for since it's used in many more
>>>> applications than just a FSB. Some refer to the bus as a system bus,
>>>
>>> "System bus" works for me. I/O bus makes more sense.
>>>
>>Let's see, system buses. PCI, PCI-E, ISA, AGP, and others are all system
>>buses. So how are you going to distinquish which one you are talking
>>about if you just use system bus? Damn, I wonder if FSB would do
>>that?🙂 I/O bus. Ditto, and you can throw HTlink into the mix too since
>>it is also an I/O bus.

> Hypertransport is NOT an 'bus' in any way, shape or form. HT is a
> point-to-point link. PCI-E and AGP are also definitely not buses,
> though I expect many people to incorrectly call them such. PCI and ISA
> are buses

True enough. Apparently some people call ducks geese too. ;-)

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

I believe this is a "setup" question. AMD has had superior processors
for quite some time now. Where have you been? AMD's superiority
began with the first Athlon processors, they had the first 64bit and
the first dual comsumer processor. It's dual kicks Intels butt big
time. Almost makes Intel look like they're in the dark ages they
are.

Assuming you already know the answer; what you may not know that most
AMD processors are unlocked and are quite easily over clocked and
Intel's are not. There is a reason, if Intels run any hotter, you
could heat your house with them.

Cooling, while not a glamorious subject, is the only thing giving you
a serious edge. Edge? Yeah, edge for tweaking, and edge for
longevity.

Gaming is not the only thing that gets a processor hot. I encode DVDs
from my old VCR tapes and writing chapters, pegs my processor for up
to 1/2 hour. That is much more an indicator of a faster processor,
then gaming is. Gaming stresses more then just the processor.

Using a TT Silent Boost cooler, my processor only gains about 4
degrees f. That's amazing.

Also, don't forget the video is just as important. Without good
video, all the processor power in the world won't help you for
gaming.
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Fri, 09 Sep 2005 11:29:38 -0400, keith <krw@att.bizzzz> wrote:

>On Thu, 08 Sep 2005 21:41:35 -0400, Tony Hill wrote:
>
>> On Wed, 07 Sep 2005 05:59:41 GMT, Wes Newell
>> <w.newell@TAKEOUTverizon.net> wrote:
>>
>> Not true at all. The original AMD Athlon had both a front-side bus,
>> connecting the CPU to the chipset, I/O and memory, and a backside bus
>> that connected the CPU to the cache chips on the Slot-A cartridge.
>> This was actually the last x86 CPU that I'm aware of which did have a
>> frontside bus (Intel had already gone to integrated cache by this
>> time).
>
>Just because the cache is integrated doesn't mean the cache isn't on the
>"back side" of the processor. The "back-side" concept was really a
>separation of the cache from the memory busses.

Ok, I'll grant that point. I would still say that it's not really an
accurate way of describing things when your 'bus' is connecting one
half of a die to the other half of the die, but I suppose it is still
a 'bus' of sorts, and certainly would be on the "backside" (relative
to memory).

-------------
Tony Hill
hilla <underscore> 20 <at> yahoo <dot> ca
 
Archived from groups: comp.sys.ibm.pc.hardware.chips (More info?)

dannysdailys wrote:
> Assuming you already know the answer; what you may not know that most
> AMD processors are unlocked [...]

Not quite. Only the FX models are unlocked.

The other models allow lower multipliers for Cool and Quiet.
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

Tony Hill wrote:

>
> It doesn't make any sense with the AthlonXP or the P4 and it makes
> MUCH less sense with the Athlon64/Opteron. Just because it's a common
> mistake doesn't make it any less of a mistake.
>

In matters of language, it does. Words lose their original meanings
and take on new meanings all the time. The notion of a bus as
something that can convey a signal is itself something of an
innovation, as a bus (or buss or busbar) was used in its original sense
to indicate something used to distribute power.

Using the term "front-side bus" to designate something other than what
the term referred to originally is an innovation, but it isn't wrong,
and it isn't even eccentric, because lots of people make the same
"mistake."

Only innovations in the ways that words are used aren't "mistakes,"
they are part of the natural process of by which language, and even
technical terminology, grows and evolves.

If there is confusion in a communication that results from a term being
used in a non-standard or ambiguous way, the confusion should be
addressed and the intended meaning clarified. Exploration of the
origins of a term and the different ways it has been used can be
enlightening and even fun.

Arguing over who is "right" and who is "wrong" just isn't any fun and
it enlightens no one.

RM
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Fri, 09 Sep 2005 22:59:53 -0400, Tony Hill wrote:

> On Fri, 09 Sep 2005 11:29:38 -0400, keith <krw@att.bizzzz> wrote:
>
>>On Thu, 08 Sep 2005 21:41:35 -0400, Tony Hill wrote:
>>
>>> On Wed, 07 Sep 2005 05:59:41 GMT, Wes Newell
>>> <w.newell@TAKEOUTverizon.net> wrote:
>>>
>>> Not true at all. The original AMD Athlon had both a front-side bus,
>>> connecting the CPU to the chipset, I/O and memory, and a backside bus
>>> that connected the CPU to the cache chips on the Slot-A cartridge.
>>> This was actually the last x86 CPU that I'm aware of which did have a
>>> frontside bus (Intel had already gone to integrated cache by this
>>> time).
>>
>>Just because the cache is integrated doesn't mean the cache isn't on the
>>"back side" of the processor. The "back-side" concept was really a
>>separation of the cache from the memory busses.
>
> Ok, I'll grant that point. I would still say that it's not really an
> accurate way of describing things when your 'bus' is connecting one
> half of a die to the other half of the die, but I suppose it is still
> a 'bus' of sorts, and certainly would be on the "backside" (relative
> to memory).

Why? There are *loads* of busses on processor chips, though most are
driven from a single end (bi-di gets messy). ...right down to the
power busses, though sometimes they're grids. ;-)

--
Keith
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

"keith" <krw@att.bizzzz> wrote in message
news😛an.2005.09.10.14.25.43.450875@att.bizzzz...
> On Fri, 09 Sep 2005 22:59:53 -0400, Tony Hill wrote:
>
>> On Fri, 09 Sep 2005 11:29:38 -0400, keith <krw@att.bizzzz> wrote:
>>
>>>On Thu, 08 Sep 2005 21:41:35 -0400, Tony Hill wrote:
>>>
>>>> On Wed, 07 Sep 2005 05:59:41 GMT, Wes Newell
>>>> <w.newell@TAKEOUTverizon.net> wrote:
>>>>
>>>> Not true at all. The original AMD Athlon had both a front-side bus,
>>>> connecting the CPU to the chipset, I/O and memory, and a backside
>>>> bus
>>>> that connected the CPU to the cache chips on the Slot-A cartridge.
>>>> This was actually the last x86 CPU that I'm aware of which did have
>>>> a
>>>> frontside bus (Intel had already gone to integrated cache by this
>>>> time).
>>>
>>>Just because the cache is integrated doesn't mean the cache isn't on
>>>the
>>>"back side" of the processor. The "back-side" concept was really a
>>>separation of the cache from the memory busses.
>>
>> Ok, I'll grant that point. I would still say that it's not really an
>> accurate way of describing things when your 'bus' is connecting one
>> half of a die to the other half of the die, but I suppose it is still
>> a 'bus' of sorts, and certainly would be on the "backside" (relative
>> to memory).
>
> Why? There are *loads* of busses on processor chips, though most are
> driven from a single end (bi-di gets messy). ...right down to the
> power busses, though sometimes they're grids. ;-)
>
> --
> Keith

And people talk about the power bus even when it is a grid. Just like
they talk about the clock tree when it is a grid. And real designers
sometimes talk about the HT bus or the RIO bus, or the GX bus even when
it is a link more than a bus.

del
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Sat, 10 Sep 2005 07:37:13 GMT, Wes Newell
<w.newell@TAKEOUTverizon.net> wrote:

>It calls it a bus (a Front Side bus at that) in the portion you snipped
>out and you know it. I don't know why you cut it out. it only makes you
>look trollish. Here's some more info for you.
>
>http://www.free-definition.com/Front-side-bus.html

Hmm, from this link, at the bottom of the chart:

"*** - Athlon 64, FX, and Opteron processors have a memory controller
on the CPU die, which replaces the traditional FSB"

>http://www.free-definition.com/category/Computer_bus

Try this one:

http://www.free-definition.com/Computer-bus.html

"In computer architecture, a bus is a subsystem that transfers data or
power between computer components inside a computer or between
computers. Unlike a point-to-point connection, a bus can logically
connect several peripherals over the same set of wires."

Hypertransport is a point-to-point connection, as is PCI-Express.
GTL+ and PCI are buses.

-------------
Tony Hill
hilla <underscore> 20 <at> yahoo <dot> ca
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Sat, 10 Sep 2005 08:33:53 GMT, Wes Newell
<w.newell@TAKEOUTverizon.net> wrote:

>On Fri, 09 Sep 2005 23:18:00 -0400, keith wrote:
>> There is no such "proof". The definition of a "bus" is much older than
>> even you. A buss is a multi-drop utility. ...kinda like what you take to
>> work. A point-to-point facility is never referred to as a "bus".
>>
>You wouldn't know the definition if it bit you on the ass. But, just to
>show how stupid this response is, the frontside bus was point to point, as
>was the back side bus. The same could be said for the memory bus. IOW's
>you don't know wtf you are talking about.

Uhh ?!?! The GTL bus used in the PPro was DEFINTIELY a multi-point
bus. You can hang up to 4 CPUs off of that bus. This is still true
(at least in some situations) for the AGTL+ bus that Intel still uses
for their P4 and Xeon CPUs.

Similarly the backside bus in the PPro, PII and early PIII chips could
definitely have more than one memory device hung off the back of it.
If my memory is serving me, some Xeon CPUs had up to 4 cache chips on
a single bus. You can't do that with a point-to-point link!

Keeping up with the memory bus it DEFINITELY is a multidrop bus with
only one popular exception that I'm aware of (RDRAM). How else do you
think you can hang more than one DIMM off a single memory bus?

EV6, on the other hand, was not a bus by the strict multidrop
definition of things in that you could NOT hang more than one
processor off the bus. That's why AthlonMP systems (and DEC/Compaq/HP
Alpha systems before it) had one bus per processor. This is a large
part of the reason why you never saw quad AthlonMP systems, only dual
processor ones. Now, that being said, EV6 resembled a bus in most
other respects, which is why I said that it kind of blurred the lines
between a traditional bus and a strictly point-to-point connection.


Now, just how strictly one follows some of these definitions of what a
"bus" is depends on the reader. I know many people (myself included)
would tend to take shortcuts most of the time. Generally speaking I
would quite freely refer to EV6 as a "bus" rather than going through
the above explanation. I'm sure I've even been known to call
PCI-Express or Hypertransport a "bus" from time to time, though I
still recognize that it's not correct.


>9. How does HyperTransport technology compare to other bus technologies?
>
>*this is the relevent part*
>HyperTransport was designed to support both CPU-to-CPU communications as
>well as CPU-to-I/O transfers, thus, it features very low latency.
>Consequently, it has been incorporated into multiple x86 and MIPS
>architecture processors as an integrated front-side bus.

That's rather poorly worded on their part and actually contradicts
other parts of the same article where they (correctly) state that
Hypertransport is not a bus at all. As mentioned above though, people
take shortcuts, sometimes even when they know it's not really correct.

-------------
Tony Hill
hilla <underscore> 20 <at> yahoo <dot> ca
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Sat, 10 Sep 2005 11:29:47 -0500, Del Cecchi wrote:

>
> "keith" <krw@att.bizzzz> wrote in message
> news😛an.2005.09.10.14.25.43.450875@att.bizzzz...
>> On Fri, 09 Sep 2005 22:59:53 -0400, Tony Hill wrote:
>>
>>> On Fri, 09 Sep 2005 11:29:38 -0400, keith <krw@att.bizzzz> wrote:
>>>
>>>>On Thu, 08 Sep 2005 21:41:35 -0400, Tony Hill wrote:
>>>>
>>>>> On Wed, 07 Sep 2005 05:59:41 GMT, Wes Newell
>>>>> <w.newell@TAKEOUTverizon.net> wrote:
>>>>>
>>>>> Not true at all. The original AMD Athlon had both a front-side bus,
>>>>> connecting the CPU to the chipset, I/O and memory, and a backside
>>>>> bus
>>>>> that connected the CPU to the cache chips on the Slot-A cartridge.
>>>>> This was actually the last x86 CPU that I'm aware of which did have
>>>>> a
>>>>> frontside bus (Intel had already gone to integrated cache by this
>>>>> time).
>>>>
>>>>Just because the cache is integrated doesn't mean the cache isn't on
>>>>the
>>>>"back side" of the processor. The "back-side" concept was really a
>>>>separation of the cache from the memory busses.
>>>
>>> Ok, I'll grant that point. I would still say that it's not really an
>>> accurate way of describing things when your 'bus' is connecting one
>>> half of a die to the other half of the die, but I suppose it is still
>>> a 'bus' of sorts, and certainly would be on the "backside" (relative
>>> to memory).
>>
>> Why? There are *loads* of busses on processor chips, though most are
>> driven from a single end (bi-di gets messy). ...right down to the
>> power busses, though sometimes they're grids. ;-)
>>
>> --
>> Keith
>
> And people talk about the power bus even when it is a grid. Just like
> they talk about the clock tree when it is a grid. And real designers
> sometimes talk about the HT bus or the RIO bus, or the GX bus even when
> it is a link more than a bus.

People call cyan, blue too. Because people get sloppy, doesn't change the
meaning of words. In technical writing, words do have meanings.

--
Keith
>
> del
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

"keith" <krw@att.bizzzz> wrote in message
news😛an.2005.09.11.00.11.52.492583@att.bizzzz...
> On Sat, 10 Sep 2005 11:29:47 -0500, Del Cecchi wrote:
>
>>
>> "keith" <krw@att.bizzzz> wrote in message
>> news😛an.2005.09.10.14.25.43.450875@att.bizzzz...
>>> On Fri, 09 Sep 2005 22:59:53 -0400, Tony Hill wrote:
>>>
>>>> On Fri, 09 Sep 2005 11:29:38 -0400, keith <krw@att.bizzzz> wrote:
>>>>
>>>>>On Thu, 08 Sep 2005 21:41:35 -0400, Tony Hill wrote:
>>>>>
>>>>>> On Wed, 07 Sep 2005 05:59:41 GMT, Wes Newell
>>>>>> <w.newell@TAKEOUTverizon.net> wrote:
>>>>>>
>>>>>> Not true at all. The original AMD Athlon had both a front-side
>>>>>> bus,
>>>>>> connecting the CPU to the chipset, I/O and memory, and a backside
>>>>>> bus
>>>>>> that connected the CPU to the cache chips on the Slot-A cartridge.
>>>>>> This was actually the last x86 CPU that I'm aware of which did
>>>>>> have
>>>>>> a
>>>>>> frontside bus (Intel had already gone to integrated cache by this
>>>>>> time).
>>>>>
>>>>>Just because the cache is integrated doesn't mean the cache isn't on
>>>>>the
>>>>>"back side" of the processor. The "back-side" concept was really a
>>>>>separation of the cache from the memory busses.
>>>>
>>>> Ok, I'll grant that point. I would still say that it's not really
>>>> an
>>>> accurate way of describing things when your 'bus' is connecting one
>>>> half of a die to the other half of the die, but I suppose it is
>>>> still
>>>> a 'bus' of sorts, and certainly would be on the "backside" (relative
>>>> to memory).
>>>
>>> Why? There are *loads* of busses on processor chips, though most are
>>> driven from a single end (bi-di gets messy). ...right down to the
>>> power busses, though sometimes they're grids. ;-)
>>>
>>> --
>>> Keith
>>
>> And people talk about the power bus even when it is a grid. Just like
>> they talk about the clock tree when it is a grid. And real designers
>> sometimes talk about the HT bus or the RIO bus, or the GX bus even
>> when
>> it is a link more than a bus.
>
> People call cyan, blue too. Because people get sloppy, doesn't change
> the
> meaning of words. In technical writing, words do have meanings.
>
> --
> Keith
Well, you wanna be picky, cyan is blue. And taupe is tan. And a link is
a bus. Just a special case is all. Just what is the difference? If I
only have two pins on a bus connection, like many PCI-X implementations,
does that make it not a bus?

I was just reporting what folks I hang around with during the week say.
What's the big deal? Saying HT is a link is more specific than saying it
is a bus, but I consider it to also be a bus. It's a floor wax and a
dessert topping.

del
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Sat, 10 Sep 2005 19:21:36 -0400, Tony Hill wrote:

> On Sat, 10 Sep 2005 07:37:13 GMT, Wes Newell
> <w.newell@TAKEOUTverizon.net> wrote:
>
>>It calls it a bus (a Front Side bus at that) in the portion you snipped
>>out and you know it. I don't know why you cut it out. it only makes you
>>look trollish. Here's some more info for you.
>>
>>http://www.free-definition.com/Front-side-bus.html
>
> Hmm, from this link, at the bottom of the chart:
>
> "*** - Athlon 64, FX, and Opteron processors have a memory controller
> on the CPU die, which replaces the traditional FSB"
>
Note the wording. It doesn't say it replaces the FSB. It says it replaces
the traditional FSB. The FSB is still there, jst not in a tradidtional
sense, since the memory has it's own path now. I'll tell you what. You can
call it whatever you like, and I'll do the same.

>>http://www.free-definition.com/category/Computer_bus
>
> Try this one:
>
> http://www.free-definition.com/Computer-bus.html
>
> "In computer architecture, a bus is a subsystem that transfers data or
> power between computer components inside a computer or between
> computers. Unlike a point-to-point connection, a bus can logically
> connect several peripherals over the same set of wires."
>
But if you use this definition, there was never a FSB, or BSB bus
as these were both point to point connections. Was not the FSB of the
original Pentium Pro point to point (cpu to chipset)? And this defintition
also disagrees with lots of other definitions of bus, and lastly, if my
system has only one memory slot, does that mean my system doesn't have a
memory bus? One sometimes one has to think logical rather than just take
something at face value.

> Hypertransport is a point-to-point connection, as is PCI-Express. GTL+
> and PCI are buses.
>
Along with HyperTransport, PCI-Express is also defined as a Computer bus.

--
KT133 MB, CPU @2400MHz (24x100): SIS755 MB CPU @2330MHz (10x233)
Need good help? Provide all system info with question.
My server http://wesnewell.no-ip.com/cpu.php
Verizon server http://mysite.verizon.net/res0exft/cpu.htm
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

Since there is no FSB to use as a reference for the CPU-core's
clockspeed (as well as some of the other clocks), we need something else
to provide the required reference clock signal.

The solution to this problem is a 200MHz base-clock provided to the
processor by the on-board clock-generator on all 8th-Generation
platforms.

This Article will explain how clocks are generated on an AMD
8th-Generation platform.
http://forums.amd.com/index.php?showtopic=55881
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Fri, 09 Sep 2005 18:23:25 -0400, George Macdonald
<fammacd=!SPAM^nothanks@tellurian.com> wrote:

....snip...
>If we allow a bit of slack and call the on-die L2 cache connection a BSB,
>we can call the K7s', P4s', P-Ms' connection to the chipset a FSB - after
>all it carries the same traffic as a FSB. AMD has used this terminology
>for its K7 architecture though some have argued with that. With the K8 the
>HT link to to the I/O sub-system, however, there is no CPU<-> memory
>traffic, which is the principal function of a FSB and is the derivation of
>the name; the up/down HT link doesn't even serve the same functions as a
>FSB.
>
....snip...

"no CPU<-> memory traffic"
Correct for uniprocessor system. As soon as we get to dual (trust me
on this - I'm typing this on 2x Opteron 242 on MSI master2-far board)
HT starts carrying CPU<-> memory traffic. It is especially true in
case of more than half dual Opty board out there (including mine)
where all RAM is hanging off one CPU, and the other accesses it
through HT.

NNN
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Sun, 11 Sep 2005 05:25:33 GMT, Wes Newell
<w.newell@TAKEOUTverizon.net> wrote:

>> "In computer architecture, a bus is a subsystem that transfers data or
>> power between computer components inside a computer or between
>> computers. Unlike a point-to-point connection, a bus can logically
>> connect several peripherals over the same set of wires."
>>
>But if you use this definition, there was never a FSB, or BSB bus
>as these were both point to point connections. Was not the FSB of the
>original Pentium Pro point to point (cpu to chipset)?

No it most definitely was not. You could hang up to 4 PPro processors
off the same bus.

> And this defintition
>also disagrees with lots of other definitions of bus, and lastly, if my
>system has only one memory slot, does that mean my system doesn't have a
>memory bus?

If you're using SDRAM or DDR SDRAM then the bus connects to each
individual chip on the module. Unless you've only got a single memory
chip on your single DIMM then this is definitely not a direct
point-to-point connection.

Besides, it's more a question of what the bus is capable of, not so
much what it is actually being used for. Just because the P4
processor itself is only capable of working in a single-processor
setup doesn't change the fact that the AGTL+ bus that it uses can be
used for up to 4 processors on the same bus (as seen in some Xeon
systems).

-------------
Tony Hill
hilla <underscore> 20 <at> yahoo <dot> ca
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Sun, 11 Sep 2005 13:52:36 -0500, Big_Pig wrote:

> Since there is no FSB to use as a reference for the CPU-core's
> clockspeed (as well as some of the other clocks), we need something else
> to provide the required reference clock signal.
>
> The solution to this problem is a 200MHz base-clock provided to the
> processor by the on-board clock-generator on all 8th-Generation
> platforms.
>
And that's exactly how previous generations platforms did it too.🙂

> This Article will explain how clocks are generated on an AMD
> 8th-Generation platform.
> http://forums.amd.com/index.php?showtopic=55881

This is a great article, but there's really no difference in the system
clock source of the K7 and K8. They both use the clkin signals. Previously
this clock was called FSB frequency or FSB clock or whatever a board
manufacurer wanted to use to set the clock generator. I think most used
FSB Frequency, but I haven't looked at all the boards bioses. So now comes
the K8 and in their wisdom (or lack of it IMO), thee decide the new bus
type of HT link shouldn't use FSB as the name like the previous K7 EV6
type bus. And that would have been fine if they would come up with another
name to set this clock. I haven't looked at many K8 boards, but it's
designated as System Bus in my bios. The big problem with that name is
that a system bus can any in the system, and isn't specific enough. Same
goes for HT link, which is really a name for a technology like EV6 is, and
is used in many applications than just the K8 CPU's. Not to mention there
can be multiple HT links in a system, so how do you know which one they're
talking about unless it spelled out. Looking back, it would have been
much better to use something like System Clock Gen or CPU Clock Gen for
this setting rather than FSB, but since we were shouldered with FSB, it
finally became known as the connection between the CPU and chipset, which
in fact it is, and that this was the setting to chnage to set the internal
cpu clock... Now that there's no FSB designated for the K8, there's also
no desgination one would easily recognize. So did AMD do away with the
FSB, or just the name because they wanted more exposure for HT or some
other reason. I contend, it was just the name they wanted to change since
the actual traces on the MB still go from the CPU to the chipset just like
previous FSB's with the exception of the memory bus. Had they keep the FSB
name, or even called it the HT FSB, there wouldn't have been the confusion
there is now. Fankly I don't care much. But since many peole don't like
the term FSB used with the K8, I'm going to start telling people to raise
the clkin frequency to the cpu to set the cpu speed and let them worry
about what there board maker called it in the bios. Now since the FSB
term was used to set clkin on previous cpu's, why is it now all of a
sudden taboo?

--
KT133 MB, CPU @2400MHz (24x100): SIS755 MB CPU @2330MHz (10x233)
Need good help? Provide all system info with question.
My server http://wesnewell.no-ip.com/cpu.php
Verizon server http://mysite.verizon.net/res0exft/cpu.htm
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

"Tony Hill" <hilla_nospam_20@yahoo.ca> wrote in message
news:m349i152drvnh2b4l5tjkojpn7dce1lleu@4ax.com...
> On Sun, 11 Sep 2005 05:25:33 GMT, Wes Newell
> <w.newell@TAKEOUTverizon.net> wrote:
>
>>> "In computer architecture, a bus is a subsystem that transfers data or
>>> power between computer components inside a computer or between
>>> computers. Unlike a point-to-point connection, a bus can logically
>>> connect several peripherals over the same set of wires."
>>>
>>But if you use this definition, there was never a FSB, or BSB bus
>>as these were both point to point connections. Was not the FSB of the
>>original Pentium Pro point to point (cpu to chipset)?
>
> No it most definitely was not. You could hang up to 4 PPro processors
> off the same bus.
>
>> And this defintition
>>also disagrees with lots of other definitions of bus, and lastly, if my
>>system has only one memory slot, does that mean my system doesn't have a
>>memory bus?
>
> If you're using SDRAM or DDR SDRAM then the bus connects to each
> individual chip on the module. Unless you've only got a single memory
> chip on your single DIMM then this is definitely not a direct
> point-to-point connection.
>
> Besides, it's more a question of what the bus is capable of, not so
> much what it is actually being used for. Just because the P4
> processor itself is only capable of working in a single-processor
> setup doesn't change the fact that the AGTL+ bus that it uses can be
> used for up to 4 processors on the same bus (as seen in some Xeon
> systems).
>

You guys must be a barrel of laughs down the pub.... ;-)

Could ya knock of the non-technical game group from future posts pls?
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

Your entire premise is wrong.

Hypertransport is a High speed, packet based control and communication
protocol. It supports the Direct Connect Architecture of the AMD Athlon64
and Turion64 processors. The processor does not use the Northbridge to
communicate to Memory/AGP/PCI/PCI-E, so there is *no* FSB speed there. The
traditional Northbridge legacy set is handled by the chip, as is the
Southbridge, but for the Proc, RAM and video there is no FSB, just the
speed/bandwidth of the H/T bus (800, 1000, 1600 or 2000). In addition, the
communication is duplex under Hypertransport, versus simplex under NB-FSB.

Bobby

"Wes Newell" <w.newell@TAKEOUTverizon.net> wrote in message
news😛an.2005.09.11.23.37.45.362968@TAKEOUTverizon.net...
> On Sun, 11 Sep 2005 13:52:36 -0500, Big_Pig wrote:
>
>> Since there is no FSB to use as a reference for the CPU-core's
>> clockspeed (as well as some of the other clocks), we need something else
>> to provide the required reference clock signal.
>>
>> The solution to this problem is a 200MHz base-clock provided to the
>> processor by the on-board clock-generator on all 8th-Generation
>> platforms.
>>
> And that's exactly how previous generations platforms did it too.🙂
>
>> This Article will explain how clocks are generated on an AMD
>> 8th-Generation platform.
>> http://forums.amd.com/index.php?showtopic=55881
>
> This is a great article, but there's really no difference in the system
> clock source of the K7 and K8. They both use the clkin signals. Previously
> this clock was called FSB frequency or FSB clock or whatever a board
> manufacurer wanted to use to set the clock generator. I think most used
> FSB Frequency, but I haven't looked at all the boards bioses. So now comes
> the K8 and in their wisdom (or lack of it IMO), thee decide the new bus
> type of HT link shouldn't use FSB as the name like the previous K7 EV6
> type bus. And that would have been fine if they would come up with another
> name to set this clock. I haven't looked at many K8 boards, but it's
> designated as System Bus in my bios. The big problem with that name is
> that a system bus can any in the system, and isn't specific enough. Same
> goes for HT link, which is really a name for a technology like EV6 is, and
> is used in many applications than just the K8 CPU's. Not to mention there
> can be multiple HT links in a system, so how do you know which one they're
> talking about unless it spelled out. Looking back, it would have been
> much better to use something like System Clock Gen or CPU Clock Gen for
> this setting rather than FSB, but since we were shouldered with FSB, it
> finally became known as the connection between the CPU and chipset, which
> in fact it is, and that this was the setting to chnage to set the internal
> cpu clock... Now that there's no FSB designated for the K8, there's also
> no desgination one would easily recognize. So did AMD do away with the
> FSB, or just the name because they wanted more exposure for HT or some
> other reason. I contend, it was just the name they wanted to change since
> the actual traces on the MB still go from the CPU to the chipset just like
> previous FSB's with the exception of the memory bus. Had they keep the FSB
> name, or even called it the HT FSB, there wouldn't have been the confusion
> there is now. Fankly I don't care much. But since many peole don't like
> the term FSB used with the K8, I'm going to start telling people to raise
> the clkin frequency to the cpu to set the cpu speed and let them worry
> about what there board maker called it in the bios. Now since the FSB
> term was used to set clkin on previous cpu's, why is it now all of a
> sudden taboo?
>
> --
> KT133 MB, CPU @2400MHz (24x100): SIS755 MB CPU @2330MHz (10x233)
> Need good help? Provide all system info with question.
> My server http://wesnewell.no-ip.com/cpu.php
> Verizon server http://mysite.verizon.net/res0exft/cpu.htm
>
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Sun, 11 Sep 2005 13:52:36 -0500, Big_Pig <big_pig@farming.com> wrote:

>Since there is no FSB to use as a reference for the CPU-core's
>clockspeed (as well as some of the other clocks), we need something else
>to provide the required reference clock signal.
>
>The solution to this problem is a 200MHz base-clock provided to the
>processor by the on-board clock-generator on all 8th-Generation
>platforms.
>
>This Article will explain how clocks are generated on an AMD
>8th-Generation platform.
>http://forums.amd.com/index.php?showtopic=55881

This one doesn't have any mistakes🙂 -
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/24707_PUB.PDF

--
Rgds, George Macdonald
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Sun, 11 Sep 2005 14:59:32 GMT, "nobody@nowhere.net"
<mygarbage2000@hotmail.com> wrote:

>On Fri, 09 Sep 2005 18:23:25 -0400, George Macdonald
><fammacd=!SPAM^nothanks@tellurian.com> wrote:
>
>...snip...
>>If we allow a bit of slack and call the on-die L2 cache connection a BSB,
>>we can call the K7s', P4s', P-Ms' connection to the chipset a FSB - after
>>all it carries the same traffic as a FSB. AMD has used this terminology
>>for its K7 architecture though some have argued with that. With the K8 the
>>HT link to to the I/O sub-system, however, there is no CPU<-> memory
>>traffic, which is the principal function of a FSB and is the derivation of
>>the name; the up/down HT link doesn't even serve the same functions as a
>>FSB.
>>
>...snip...
>
>"no CPU<-> memory traffic"
>Correct for uniprocessor system. As soon as we get to dual (trust me
>on this - I'm typing this on 2x Opteron 242 on MSI master2-far board)
>HT starts carrying CPU<-> memory traffic. It is especially true in
>case of more than half dual Opty board out there (including mine)
>where all RAM is hanging off one CPU, and the other accesses it
>through HT.

Of course but that's really CPU<->CPU traffic... which is why I made a
point of clearly specifying the "HT link to the I/O sub-system". Lifting
quoted text out of context only confuses the issue.

--
Rgds, George Macdonald
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Mon, 12 Sep 2005 01:21:57 +0000, NoNoBadDog! wrote:

> Your entire premise is wrong.
>
> Hypertransport is a High speed, packet based control and communication
> protocol. It supports the Direct Connect Architecture of the AMD Athlon64
> and Turion64 processors. The processor does not use the Northbridge to
> communicate to Memory/AGP/PCI/PCI-E, so there is *no* FSB speed there. The
> traditional Northbridge legacy set is handled by the chip, as is the
> Southbridge, but for the Proc, RAM and video there is no FSB, just the
> speed/bandwidth of the H/T bus (800, 1000, 1600 or 2000). In addition, the
> communication is duplex under Hypertransport, versus simplex under NB-FSB.
>
You're just a little more than confused. The CPU doesn't support AGP, PCI,
PCI-E or much of anything else except the ram directly. The rest still are
still functions of the chipset. The only thing that the CPU now supports
directly is the memory. All other system devices/buses are handled the
same way as the K7 was, over the FSB, or if you prefer, the HT Link
between the cpu and chipset.

--
KT133 MB, CPU @2400MHz (24x100): SIS755 MB CPU @2330MHz (10x233)
Need good help? Provide all system info with question.
My server http://wesnewell.no-ip.com/cpu.php
Verizon server http://mysite.verizon.net/res0exft/cpu.htm
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

On Mon, 12 Sep 2005 06:07:42 GMT, Wes Newell <w.newell@TAKEOUTverizon.net>
wrote:

>On Mon, 12 Sep 2005 01:21:57 +0000, NoNoBadDog! wrote:
>
>> Your entire premise is wrong.
>>
>> Hypertransport is a High speed, packet based control and communication
>> protocol. It supports the Direct Connect Architecture of the AMD Athlon64
>> and Turion64 processors. The processor does not use the Northbridge to
>> communicate to Memory/AGP/PCI/PCI-E, so there is *no* FSB speed there. The
>> traditional Northbridge legacy set is handled by the chip, as is the
>> Southbridge, but for the Proc, RAM and video there is no FSB, just the
>> speed/bandwidth of the H/T bus (800, 1000, 1600 or 2000). In addition, the
>> communication is duplex under Hypertransport, versus simplex under NB-FSB.
>>
>You're just a little more than confused. The CPU doesn't support AGP, PCI,
>PCI-E or much of anything else except the ram directly. The rest still are
>still functions of the chipset. The only thing that the CPU now supports
>directly is the memory. All other system devices/buses are handled the
>same way as the K7 was, over the FSB, or if you prefer, the HT Link
>between the cpu and chipset.

You have just proved your complete misunderstanding of what is on the K8
die and what the HT I/O-link is used for. All CPU memory accesses mapped
to I/O devices, such as AGP/PCI-e, or any PCI device must be trapped in the
CPU's "north bridge" sub-set and diverted to the HT I/O link; obviously the
corresponding MTRRs and associated logic *must* be on the CPU die. Same
for CPU cache snooping - previously a north bridge/FSB function and now
incorporated into the CPU.

Apart from CPU I/O reads/writes and interrupts, a minor part of FSB traffic
"volume", the HT I/O link has nothing in common with a FSB. The major
volume of traffic on the K8 HT I/O-link, viz. DMA transfers, is handled and
routed internally in the north bridge (MC Hub) of a FSB type system.

--
Rgds, George Macdonald
 
Archived from groups: comp.sys.ibm.pc.hardware.chips,alt.comp.hardware.amd.x86-64,comp.sys.ibm.pc.games.action (More info?)

"Wes Newell" <w.newell@TAKEOUTverizon.net> wrote in message
news😛an.2005.09.12.06.11.55.449547@TAKEOUTverizon.net...
> On Mon, 12 Sep 2005 01:21:57 +0000, NoNoBadDog! wrote:
>
>> Your entire premise is wrong.
>>
>> Hypertransport is a High speed, packet based control and communication
>> protocol. It supports the Direct Connect Architecture of the AMD
>> Athlon64
>> and Turion64 processors. The processor does not use the Northbridge to
>> communicate to Memory/AGP/PCI/PCI-E, so there is *no* FSB speed there.
>> The
>> traditional Northbridge legacy set is handled by the chip, as is the
>> Southbridge, but for the Proc, RAM and video there is no FSB, just the
>> speed/bandwidth of the H/T bus (800, 1000, 1600 or 2000). In addition,
>> the
>> communication is duplex under Hypertransport, versus simplex under
>> NB-FSB.
>>
> You're just a little more than confused. The CPU doesn't support AGP, PCI,
> PCI-E or much of anything else except the ram directly. The rest still are
> still functions of the chipset. The only thing that the CPU now supports
> directly is the memory. All other system devices/buses are handled the
> same way as the K7 was, over the FSB, or if you prefer, the HT Link
> between the cpu and chipset.
>
> --
> KT133 MB, CPU @2400MHz (24x100): SIS755 MB CPU @2330MHz (10x233)
> Need good help? Provide all system info with question.
> My server http://wesnewell.no-ip.com/cpu.php
> Verizon server http://mysite.verizon.net/res0exft/cpu.htm
>
Re-read what I wrote...I did not say that it did, but that the
hypertransport bus allows greater bandwidth and duplex operations. The
memory controller accesses the cache and RAM data.
The NB is legacy, while the SB still functions in a traditional manner.

Bobby
 

TRENDING THREADS