Slashdot Mirror
Understanding 64-bit PowerPC architecture
An anonymous reader writes "Each of the leading microprocessor manufacturers has announced the availability of one or more 64-bit desktop processors, but differences exist in architectural design, fabrication, support, and intended use of each processor. This article looks at the critical issues in a few of IBM's 64-bit POWER designs, covering 32-bit compatibility, power management, processor bus design, and the manufacturing process."
It's a dupe.
Power != PowerPC That is all.
Didn't I just read about this?!
The heat is on
Isn't this the same story as five stories ago? Am I missing something?
Right here. And why yes, the dupe is still on the front page, why do you ask?
``64 bit PowerPC architecture...desktop...POWER''
but wait...I thought PowerPC and POWER are similar, but not identical, and that PowerPC was aimed at the desktop, whereas POWER is more for servers. Do I have it wrong?
Please correct me if I got my facts wrong.
...takes a good look at duping.
That is the first time I've seen a dupe at the same time as the original is on the front page. Wow again.
-._''_.-
The fastest dupe I've ever seen.
this type of thing happens all the time. Same story posted again... probably just a symptom of my time shifting
a dupe posted by CmdrTaco to a story posted by Hemos.. It feels like 1998 again :-)
that AMD wasn't the first, but they're Athlon line is really top notch. I have two already, and I recommend it to everyone I know.
Free Desk
Let's see if they go for the record and post this story a third time before the first one goes off the front page.
What Would Jesus Do
(for a Klondike bar)?
i think they did that because the other link is still loadable
unlike the watercooling article
Admit it! Some of you send in stories that are on the front page just to see if they get duped, right?
I'm on to you!
Fellowship 9/11
Here are some other interesting stories
m icrodesign/?ca=dgr-lnxw01fkjfdsa m icrodesign/?ca=dgr-lnxw01dhifads m icrodesign/?ca=dgr-lnxw01jj5324543 m icrodesign/?ca=dgr-lnxw01hdshdgh m icrodesign/?ca=dgr-lnxw01jesusheadfuck
http://www-106.ibm.com/developerworks/library/pa-
http://www-106.ibm.com/developerworks/library/pa-
http://www-106.ibm.com/developerworks/library/pa-
http://www-106.ibm.com/developerworks/library/pa-
http://www-106.ibm.com/developerworks/library/pa-
Slashdot's nondiscrimination policy prevents them from excluding dupes on the basis of topic of origin.
their means belonging to them.
they're means "they are"
there means not here.
First, I'm talking a risc/cisc architecture like the x86.
:P.
When you're talking about 64 addressing lines, your talking about addressing a fscksum of memory and devices. But, in addition, those lines allow for other possibilities: for example, sending 2 or 3 write commands with attached data and 2 32 bit addresses on the 64 bit bus simultaniously with an extra address decoder either on the chip or on the memory controller, or to some other device. Although, I don't know weither or not they've thrown that in as of yet. 64 bit numbers don't occur that often, afaik, but I'm not a coder so
The data bus advantage, however, is bigger. The x86 architecture has a command decoder, whereas you can send several commands in a single clock. With 32 more bytes, you get twice as many commands in a clock. Additionally, you can address more commands (but seriously, the first x86 had 38 commands, and that has increased by 10x in the past few years).
Aside from that, you're throwing on more features into the processor. But, that's been here in the past 20 years of processor developement anyway. The article tends to be unclear on this. You're essentially expanding the bus to feed more buffers/pipelines.
Candy-Coated Knowledge
I, for one, welcome our new 64-bit overlords!
I saw the same black cat walking by a moment ago.
Together, we are strong; Apart, we are stronger.
I did my afternoon slashdot break. I'm hitting "reloading" thinking, my company must be caching the pages now or something... No new stories. Whats going on.
and on and on and on....
There is no reason why a bios based OS cannot become viable in 64 bit registers. The maddening thing about the PC, which ever flavour, is that you still need to boot from a hard drive. It would be really great if the future of computing was to eliminate the need to store the OS on a drive. This would substantially reduce, 1. boot error (due to bit rot), 2. overall system speed. This in combination with hardware with built in brains, would change computing. This change would only be for the better. Security, speed, ease of use and compatability could all be enhanced. The monolith in Redmond would actually start to feel some heat from real competition.
Puff Apple stories get more clicks for slashdot.
... so there's a big downside)
(Of course, it brings out the pro-apple moderators, too
The correct word is TRIPE.
My amazing wife - Artist, Author, Philosopher - Laurie M
What we realy need is a method to moderate the stories themselves - not just the commnets. Can ya see it now? "-5 Dupe"
Some of the stories that do get accepted, it's stunning what gets front page exposure. While other stories that get rejected - you know, real news that nerds could use...
It's time to extend the voice of the community
Senior NCO in the fight against entropy. I've seen things, man. Things no one should have to see.....
no. It's not a dupe, it's the 64 bit bus sending the same 32 bit information, doubled up along the bus. It's just looks like it's posted twice. It's much more efficient this way. Trust us!
no. It's not a dupe, it's the 64 bit bus sending the same 32 bit information, doubled up along the bus. It's just looks like it's posted twice. It's much more efficient this way. Trust us!
You guys sux on mathematics: if it was a dupe, it would be an article talking about 128-bit stuff, you fools !
Yes, that fits much better.
In the abscence of institutional memory or /. editors sitting in the same room :-) , could Slashcode be tweaked to scan for URLs that are identical in stories and flag them somehow?
Some Perl script or such that looks at the post about to hit the front page, then looks at a say the last three or four posts that were on the front page. If it finds an identical or closely identical link, it then sends an email of the body of the two posts to the editor.
I don't think it would get the server's load up too much.
(much sarcasm, minus 1, bad dog.)
the future is here, it is just not evenly distributed - w. gibson
Anyone?
That would be a trip. Remember, dupe is short for duplicate. The correct abbreviation for three stories would be "trip", which is short for "triplicate" (which is a real word, yes).
...
The real question is why I'm debating the correct abbreviations for Slashdot editorial errors on Slashdot
Timothy, you're really the only editor on Slashdot who manages such an amazing amount of dupes. And you're also the only one that manges to post dupes of articles that are still on the front page.
:D
I heard the Guiness Book of Records called.
give ya credit for that.
Thank Allah.
...who else would mod this down to -1?
Actually, they are trying to slashdot IBM, and the first one didn't do it, so up went a second. Unfortunately IBM's webserver is a z-server. I expect we will see a few hundred more dupes until they give up.
If it gets posted twice...well, let's just say this thread will be the ultimate power in the universe.
Threads are mammals?
It's not offtopic, dumbass. It's orthogonal.
That would be a trip. Remember, dupe is short for duplicate. The correct abbreviation for three stories would be "trip", which is short for "triplicate"
:)
Yes, but if you use the same transformation...
duplicate -> dupe
triplicate -> tripe
I'd argue that tripe is actually well fitting in that pure sense. That fact that it has pun value is an added bonus!
pointers are twice the size, take up more room in L1/L2/L3 cache, less room for other things, more cache misses. Likewise, ram and swap.