Voltage + ? = Processor Frequency

[linux_0]

lol 😀

I do both. I build them and use / admin them... I also break them ;-) :lol:

You ever try Linux or BSD?

 

[MadModMike]

Joset, thank you for cramming my 6 paragraphs into 1, but those exact words came from a website, I know this because I read that same thing a few months ago, thanks for the refresher though, I had forgotten what Intel called their memory controller.

Linux: We use many variations of Linux in my Microsoft Certified Systems Administrator program (weird, eh?) and I prefer Windows, only because of software support, but I do believe Windows to be as stable as a Prescott CPU under 30c (Hell musta froze over if that happened, lol). Only thing that sucks is that we have nearly 40 PC's in our lab in which it feels like we reinstall Server 2003 every single day, due to some mishap with DHCP or a configuration gone wrong.

BTW, I suck at crimping RJ-45 cables, but I am the master of ghettoniss. Can't beat making the wires 5" too long and than crimping the connectors on and taping the plastic shielding back on the wires to cover 'em up, I'm so cool 8).

~~Mad Mod Mike, pimpin' the world 1 rig at a time

 

[ltcommander_data]

The Memory from the Memory Controller on Intel CPU's is accessed at 200MHz Double Data Rate (400MHz Effective) where it accesses RAM at 400MHz and receives at 400MHz, UniDirectional (not at the same time). On AMD64 CPU's, it accesses information at 1GHz and receives at 400MHz BiDirectional (at the same time).

I don't mean to be picky, but I believe you got the buses mixed up. Intel's FSB is bidirectional, while HyperTransport is unidirectional. The difference is that the FSB design is half duplex, while HyperTransport is fully duplex. This means that a single FSB can send data in either direction, but only in one direction at any one time, while HyperTransport uses two buses, each one permanently sending data in a given direction.

http://www.hypertransport.org/tech/index.cfm

I also thought that the memory to memory controller speed on Intel systems was 266MHz, 333MHz, and 400MHz for 533MHz, 667MHz, and 800MHz in Double Data Rate Mode versus 200MHz for 400MHz DDR in AMD due to the use of DDR2 in Intel systems. Intel systems have the memory bandwidth advantage, while AMD systems have the latency advantage. This fits into the Netburst philosophy of raw power versus the K8's efficiency.

 

[linux_0]

LOL.... with Linux you have to screw the system up REALLY badly to have to reinstall it.

Once a day??? Geez... that's a lot

 

[MadModMike]

When I said "BiDirectional" and "UniDirectional", I was meaning Full Duplex and Half Duplex, but I should have been more thorough, thank you for pointing that out. Another correction I need to make, is the packets are 32-bit, but if the "job" requires it, HyperTransport can send 64-bit packets.

Linux: It's because other people are idiots. "Hey, here's a .SYS file, let's delete it!". But we use BCCD and Knoppix mostly, with BCCD we clustered a few computers, but couldn't find software to use for benching or performance testing, if you know of any, that'd be nice to know.

~~Mad Mod Mike, pimpin' the world 1 rig at a time

 

[joset]

Although you replied to Pat, i must congratulate you for your thread. I would say that - apart the small 'slice' which concerns my topic - it's a wonderful piece of info. Thanks for the time taken.

I didn't ask for an explanation (although enlightening as it was) as how a CPU works; I know the "hows". My quest has - only - to do with «On a processor, there is a clock setting inside the CPU programmed into it by a AMD or Intel programmer. It does not matter where this physically resides because you aint gonna edit it.» you mentioned. Certainly, it matters what & where this "unit" is and how it works. It's the only piece i'm interested in right now and, despite my search, i came out empty handed.
I'm also sure that programmers (either Intel's or AMD's) have something to do with it though i believe it's more a matter of design & engineering...
You would agree that a programmer would be useless programming a piece of hardware he doesn't know what or where it is, wouldn't you?

I don't intend to edit it. Just out of curiosity...
Maybe, it's harder a question than i thought. I'll keep searching, for sure.

Thanks, anyway.


Cheers!

 

[linux_0]

IIRC spec makes a Linux version of their benchmarks check http://spec.org

For disk benchmarks check out IOZone

that's what I used for these disk benchmarks: https://spare2.com/bench/index.html

Also there are many other benchmarks you can run too...

check http://freshmeat.net/

http://freshmeat.net/search/?q=benchmark&section=projects&Go.x=0&Go.y=0

and

http://www.google.com/search?hl=en&q=linux+benchmarks&btnG=Google+Search

😀

 

[MadModMike]

When you first posted, you sounded like you were going to try and do something with it (beyond me how you would). And yes, the designers of the CPU know where it is, but with each chip it is physically different, only way to really find out that indepth of information is to talk to a person in the company, or get lucky and read a post from somebody who really knows the answer to where it lies in the chip, good luck either way.

Linux: Thanks, gonna check themz out .

~~Mad Mod Mike, pimpin' the world 1 rig at a time

 

[Vile]

Amazing info! Thanks a lot, you really cleared out a lot of doubts I had! 😀