Speculations Intel's Next Generation 329
An anonymous reader writes "The Inquirer speculates about the next generation Intel chip. It's low power, 64 bit, multi core (up to 16?) and the real reason for the Apple switch."
Reality must take precedence over public relations, for Mother Nature cannot be fooled. -- R.P. Feynman
Intel (Score:4, Funny)
Re:Intel (Score:5, Funny)
Re:Intel (Score:3, Funny)
What with dumping all the old technology for a brave new approach, they'll undoubtably revisit old mistakes.
it'll be a 63.999999999999976581 bit processor
Re:Intel (Score:3, Insightful)
Wow!! This could mean they might catch up to AMD's current generation
I am so upset about 64 bit busses (Score:4, Interesting)
In any case, the fact that everyone wants to jump to 64 without testing the waters very carefully first is seriously foolish. I know I'm not the only one who feels this way -- Microsoft's Windows speech recognition subsystem refuses to run on any 64 bit architecture unless all of the OS and applications are strapped to 32 bit mode.
This is possibly worse than five years ago when people were paying absurd premiums to go from 800 MHz to 1.3 Ghz with RAM speeds stagnant. At least then you got something more from algorithms which weren't memory access-bound. From 32 to 64 is a significant step backwards in many cases.
Re:I am so upset about 64 bit busses (Score:4, Interesting)
The best thing in the x86-64 API is they just added a lot more registers [hardwaresecrets.com] which are sorely lacking in IA32. 8 new registers and 8 SIMD registers can help performance a lot if you compile for them.
Are you compiling for and taking advantage of all the new registers?
They might have an even better chip if they had just tacked on the new registers on IA32 but since they were breaking the ABI anyway you can understand why they would go 64 bit since it has longer legs for the future. There are going to be more and more applications that will need 64 bit as RAM and disk capacity grows, and people start working with bigger data sets.
Running Gentoo on amd64 is a bit bleeding edge. There are still a lot of apps that are masked out for it, partially just because no one tests and owns them since the user community is still pretty small. I find most things work fine when you unmask them. I need to start volunteering to support the packages I use that no one has blessed for amd64.
Re:I am so upset about 64 bit busses (Score:3, Funny)
You just made that up to see if we're paying attention, didn't you?
Re:Intel (Score:5, Funny)
Yep. My Xeon desktop runs on mumbo-jumbo and brand identity.
Intel: The Next Generation (Score:5, Funny)
Re:Intel: The Next Generation (Score:3, Funny)
Re:Intel: The Next Generation (Score:5, Funny)
Re:Intel: The Next Generation (Score:3, Funny)
Imagine poor Mr. Data's hot-headed brother Lore running AMD...
The balding captain they got. Look! (Score:2)
Now the only thing left is the klingon and the android.
Re:Intel: The Next Generation (Score:5, Funny)
Picard: "Damn those Borg! Worf! Assemble a security to format the drives!"
Worf: "Aye sir!"
Data: "Captain we have a message from the Borg Ship."
Picard: "On screen!" *gasps* "It's you!"
Bill: "Lower your shields! Resistance is futile! Superior processors is futile! Multi-core threading is futile! You will be bloated! Res..."
Picard: *motions to Data to turn the screen off* "Number 1, what you would recommend?!"
Riker: "What was that ancient Vulcan saying 'What Intel giveth, Microsoft taketh away'..."
Data: *ligh bulb expression* "Perhaps we could turn the Intel processors on the borg... Perhaps if we installed OS X for the X86"
Geordi: "...if we couple the SSE3 with our current intel processor, download the torrent, and reverse the polarity... *pauses* it just might work!"
Picard: "Make it so!"
Speculation is useless (Score:4, Funny)
Re:Speculation is useless (Score:5, Funny)
Only if you make a beowulf cluster out of them.
Re:Speculation is useless (Score:5, Funny)
maybe if you said 'megafauna' instead of turtles...
Turtles are cooler than Megafauna. (Score:3, Insightful)
Re:Speculation is useless (Score:2)
Re:Speculation is useless (Score:4, Insightful)
Re:Speculation is useless (Score:5, Funny)
Re:Speculation is useless (Score:2)
Re:Speculation is useless (Score:4, Funny)
Re: (Score:2)
Re:Speculation is useless (Score:4, Funny)
Will it run Linux?
Re:Speculation is useless (Score:2)
What do you mean run? He said "composed entirely of turtles". You must have watched too many cartoons, real turtles don't run!
Re:Speculation is useless (Score:3, Funny)
Will it crawl Linux?
Re:Speculation is useless (Score:5, Funny)
I bet it runs LOGO [mit.edu] really quick.
Re:Speculation is useless (Score:3, Funny)
But will it arrive in time (Score:5, Interesting)
If they're announcing an archtecture this radical at next week's IDF, what are the chances that it will be available and running well in time for Apple's announced timeline for desktops?
Or is Apple going to sell a lesser version first, in which case why haven't they already switched over to selling it to early adopters already. Yes there really are people who buy systems and wait for the applications to arrive later.
Re:But will it arrive in time (Score:3, Interesting)
That isn't even neccessary sometimes. I've found that of my application use on my Mac, 95+% is Apple supplied (Safar, Mail, Terminal, iLife, etc). After that, MS Office (which I expect would be ready, but would run well enough in Apple's binary translator), and BBEdit (which
Re:But will it arrive in time (Score:3, Interesting)
Re:But will it arrive in time (Score:4, Interesting)
Re:But will it arrive in time (Score:3, Interesting)
Re:But will it arrive in time (Score:2)
Servers for all! (Score:2, Insightful)
Re:Servers for all! (Score:4, Insightful)
Re:Servers for all! (Score:3, Insightful)
Soon after the G5 was introduced, IBM merged their semiconductor and server groups. The big Xserve sales such as VATech et al were potentially IBM server sales that didn't happen. The good deals on G5s that Apple got didn't make any sense if they also cost IBM server sales.
If you were IBM, would you continue that relationship?
Re:Servers for all! (Score:4, Insightful)
Re:But will it arrive in time (Score:3, Insightful)
Re:But will it arrive in time (Score:2)
I call BS.
There is Xeon, and Itanium.
-nB
Re:But will it arrive in time (Score:2)
I call BS. There is Xeon, and Itanium.
Itanium uses the AMD64/EM64T instruction set? What's IA-64 then?
Re:But will it arrive in time (Score:5, Insightful)
The few Xeon and Pentium 4 processors that do use EM64T have not been around for very long. The vast majority of Intel's processors are still 32-bit. They don't have anything that Apple could offer in a reasonably-priced desktop. Compare with AMD, which is almost entirely focused on AMD64 now, from the cheaper Athlon64s to the gamer-oriented FX series to the dual-core X2s.
Re:But will it arrive in time (Score:5, Insightful)
Re:But will it arrive in time (Score:3, Interesting)
AMD has been doing way too well for Intel not to notice. They learned lessons with the p4 (don't listen to the marketing department as much) and I don't think that the best answer they have is lackluster additions to the p4.
Things like process shrinks, more cache and slapping 2 cores together without much regard for on die communications are not revolutionary. These things can be interpreted as trying to
Re:But will it arrive in time (Score:4, Insightful)
I'd say slim to none, leaning heavily towards none. But I think that's a lot less important than your next question ...
Or is Apple going to sell a lesser version first, in which case why haven't they already switched over to selling it to early adopters already. Yes there really are people who buy systems and wait for the applications to arrive later.Apple hasn't switched over because consumers won't buy any box that doesn't run OS X apps, Macintel or not. Developers need the head start.
However, Apple and Mac developers don't have backward compatibility issues; whatever processor Intel serves up can't break code that doesn't exist. All Apple needs to do is make sure that the Xcode compilers are ready for the neXt86 processor such that what developers are compiling now will run on the new processor.
It's highly unlikely that the neXt86 will be that different, but the fact that the Mac is a clean slate means it's impossible to rule out. This is wild speculation, but Apple may be able to use this advantage to exploit the new processor's features in a way that Windows developer can't. Think of the marketing coup for Apple and Intel.
Intel may even use Apple to compel Windows developers to adopt new processor features much the way Apple spurred the USB device market.
On the other hand, the neXt86 may only sport fins and a racing stripe. :-j
Re:But will it arrive in time (Score:3, Interesting)
Entrenchment of existing code base. Windows and Windows apps already have sections of code written towards existing x86 features. The payoff for using new features must be large enough to make overhauling such code worthwhile.
Alternatively, Apple will be targeting some solutions with x86 code for the first time. Obviously A
Re:But will it arrive in time (Score:3, Informative)
All the rumors I have heard seem to suggest that the high-end desktop hardware (PowerMac, XServe, high-end iMac configs) will be the last to switch to Intel.
If Apple uses Pentium M and its successors to solve its laptop/Mac Mini problem, it can probably afford to wait on the high-end hardware. IBM has already announced [appleinsider.com] dual-core G5s which should be good for another PowerMac revision or two.
By that time, if there is a mythical Intel 64-bi
Re:But will it arrive in time (Score:3, Informative)
VLIW is basically to move a lot of the 'smarts' like instruction reordering and branch prediction from the CPU to the compiler. Thus freeing up a lot of transistors that can be used for cache or additional ALUs.
The compiler has to be very good, though. And you also run into problems like having to recompile when the next generation of the C
A lot like Sun's Niagara (Score:5, Informative)
Re:A lot like Sun's Niagara (Score:2)
faster on what ? (Score:3, Interesting)
That's good for sun, because they sell server stuff, but for other kinds of workloads this approach is very innefficient. See the Piranha [mit.edu] research paper, by Barroso et al.
Re:faster on what ? (Score:2)
Maybe we will wind up with a bunch of niagra-like simple cores for paralell code plus a small number of big, complex out-of-order execution cores for whatever hasn't (or can't be) implemented in that manner. In fact, isn't that what the Cell processor is?
Re:A lot like Sun's Niagara (Score:2)
anything is faster than 4 way xeons (Score:5, Insightful)
1 xeon = 100%
2 xeon = 140%
3 xeon = 160%
4 xeon = 170%
Wheres with the amd opteron with hyperTransport interconnect the processors dont have to fight for resources. And performance scales much better along the lines of:
1 opteron = 100%
2 opteron = 180%
3 opteron = 250%
4 opteron = 310%
Speculation based on Itanium (Score:5, Insightful)
This is the same thing Intel did to HP who walked away from PA/RISC, and to SGI who walked away from MIPS, and to Compaq/DEC who walked away from Alpha --- so they turned from the leaders in 64-bit computing to resellers of wintel.
Hey, if it worked last time, let's try it again; and maybe the rest of the 64-bit competitors'll give up.
Speculation based on Transmeta (Score:2)
But it is all pure speculation.
Re:Speculation based on Itanium (Score:2, Interesting)
The failure of the other architecture is not just Intel's successful
Re:Speculation based on Itanium (Score:2)
All just speculation... (Score:5, Insightful)
Re:All just speculation... (Score:3, Insightful)
Will happen:
Will not happen:
Possible:
Re: skeptical (Score:5, Funny)
With this tiny font, I couldn't make out what the word there was, but after reaching for my skeptacles it was all clear. Truly the wealth of alternative spellings on Slashdot never ceases to surprise. I'm not even a native English speaker.
Re:All just speculation... (Score:2)
Will we? Will they do a demo of a 4 GHz P4 [geek.com] too? Will they tell us it will use just as little power as the new Transmeta processors again?
And will anyone believe them?
core speed (Score:2, Funny)
Re:core speed (Score:3, Funny)
And at 256 times the price, it's a bargain!
Rosetta (Score:5, Interesting)
Re:Rosetta (Score:2)
Yes... I also thought of this for a second, but there's a counterpoint; the native ISA will have the freedom to be changed radically, while x86 is the stable ISA that is visible outside. I think this is a good thing (just like the fluctuations in the Linux module API) because it allows for faster development.
Re:Rosetta (Score:5, Insightful)
At one point, Transmeta was promising to be able to change the CPU on-the-fly from an x86 to other things (eg. ARM, MIPS), which is no problem, since it was doing the x86=>native translation anyway, all it has to do is change to a different translation.
So, all Intel needs to do is make the CPU be able to be switched from x86 to PPC at runtime. That's why Apple claims they can run old apps so quickly.
Re:Rosetta (Score:2, Interesting)
Theoretically, it would have been possible and was good marketing buzz so Transmeta never squashed the
Re:Rosetta (Score:2)
This would be cool. But what would be the point of sending out developer machines that are X86 based? Why would they bother with the OS-X x86 port then?
-ft
I speculate... (Score:2, Interesting)
1. Four cores standard
2. Chips pluggable to the mobo like Atari cartridges to eight CPUs
3. Mobos as blades to passive backplanes
4. Home blade servers and thin clients.
I think in the end we'll see low-end, mid-range, and high-end blade everything in the future with modularity being the way of everything.
But that's just my speculation.
There's no way this guy is right (Score:2, Interesting)
the real reason for the Apple switch (Score:2)
Apple didn't switch over for a chip (Score:5, Insightful)
It's one less thing to defend.
Back when Apple first introduced PPC (1994?), they were hyping it throughout because that was one of the few real tangible differences they could tout - pre-OSX Mac was buggy and unstable single-threaded OS while Microsoft had at least NT technology.
Now OS X pretty much rocks and they still have their excellent hardware integration - they don't need a different chip to differentiate them - OSX is their added value.
Re:Apple didn't switch over for a chip (Score:2)
yes but (Score:2)
Re:Apple didn't switch over for a chip (Score:2)
Re:Apple didn't switch over for a chip (Score:2)
pre-OSX Mac was buggy and unstable single-threaded OS
Wow. 3 false statements in one sentence only.
Tell us in what way Mac OS {10-n } was a) buggy b) unstable and c) single-threaded?
I'd really wish you'd tell me where Mac OS failed on you? Anything that was OS-related?
I've had better uptimes in Mac OS 8 and 9 than any version of Windows you can throw at it. Right up to XP.
Mac OS was threaded. In various ways. There was the Task Manager [apple.com], the Vertical retrace ma [apple.com]
Re:Apple didn't switch over for a chip (Score:2)
Re:Apple didn't switch over for a chip (Score:3, Informative)
Miss-behaving applications could bog down other applications because Mac OS used "cooperating" multi-tasking. An application, through it's normal course of operation, would relinquish CPU time through it's event loop(s).
It's a transparent process done simply by polling the system for your next user, system or idle event (aka, "WaitNextEvent()"). This is where Mac OS' multi-tasking defers from preemption modern OSes offer (Linux, Unices including OS X and Windows). In those OSes, the kernel is the one
Re:Apple didn't switch over for a chip (Score:2)
My house doesn't have circuit breakers and somehow this makes me more careful with electrical appliances. When a shorted toaster burns down the house, I don't make the same mistake twice.
I mean, I'm as much of an Apple fan as anyone, but really...
Yes, classic MacOS had advantages, especiall
Re:Apple didn't switch over for a chip (Score:4, Informative)
(a) is a matter of opinion. (b) isn't; an OS where a single application failure can easily bring down the whole system is unstable by definition. (c) is technically false, but effectively true. The Thread Manager only supported cooperative threads, which doesn't really count. You could create preemptive threads with the multiprocessing API, but they were very limited as to what they could do (no memory allocation IIRC).
I'm a Mac fan too, but there's no denying that the internals of Mac OS pre-X sucked. I still preferred it to Windows because of the UI, but I'm very pleased that with OS X I no longer have to make that tradeoff.
Re:Apple didn't switch over for a chip (Score:2)
Re:Apple didn't switch over for a chip (Score:3, Interesting)
In related news... (Score:4, Funny)
INSIDE INFORMATION (Score:5, Funny)
Who told me? The mold that lives in the back of the fridge in the second snack room on the 7th floor of the 4th building at their 2nd site.
Bwhahahahahahahaha.
OOOh i just had a thought! (Score:2)
Can this be good for Virtual Machines? (Score:3, Interesting)
Or it could be that the software JVM of today produces good enough native code for any architecture (x86, ultrasparc, ppc) that it makes it pointless to try to implement a machine that interprets the classes directly?
Wow. (Score:5, Insightful)
Apple is not that spectacular in terms of choosing chips for performance, from their past history. M68k: good chip, but it was suffering from old age when they moved to PowerPC. (They could have moved to x86, arm, or other processor at that time.) Now, they announce they are moving to Intel, and suddenly Intel has some super-duper chip up their sleeve? I don't think so.
The article starts from that basis and works up to Intel has some super-killer CPU.
Despite the amount of hype surrounding dual-core, unless you massively change software (likely to happen eventually) to support SMP, things go slower on dual-cores than single core processors, if the dual-cores are clocked lower (Intel's current chips). What the article proposes is to duplicate the mistakes Intel has made with Itanium. (It was announced a decade ago. (If not, near enough to count.))
Itanium 1 stripped out all the branch prediction, and similar things, relying on the compilers to do it. The result was that it got soundly thrashed by other 64-bit archs.
So why does Itanium 2 not suck nearly as bad? HP's engineers mostly went back and put all that stuff back IN, because compilers, and code translators are still (with a very very few exceptions, I can think of 2 (one, FX!32, mentioned in the article)) very slow. Even FX!32's speed wasn't due to the speed of translation, it was due to the huge (at the time) performance of the underlying alphas. Sure, it may have been faster than the fastest x86 hardware implementation, but it was still quite slow compared to the native speed of the chip it was on.
So the article speculates that Intel is indeed going to repeat the mistakes of the past, mistakes that *only* came to market because a) Intel has money b)Intel has pride (oh and c)got others to wipe themselves out... except IBM.) I would think Intel would learn from it's mistakes. Right now they should notice that a)processors can't be fabbed right now to work at ~4GB reliably and they are really hot. b)Going the opposite route of improving IPC almost entirely (IA-64s are not low-powered, nor cheap). Instead they should work on the in-between, which they (again due to Intel having tons of money) have in the form of the Pentium M.
It would also be stupid and out of character (Score:3, Insightful)
It would also be a moronic move business wise. Apple will be a major account for Intel, but not even close to the biggest. He'll I'd be supprised if they were even approach 10%
Re:Wow. (Score:3, Informative)
I agree that this is common wisdom, but this could also be why Apple would be a nice customer. Apple's desktop have been SMP for years now, and a lot of software has been engineered to take advantage of it. Most of the high level libraries built in OS X li
Speculation (Score:4, Funny)
A: A bunch of slashdotters doing the same thing.
Same fool, same laughs (Score:5, Informative)
Seriously, it's worth a read for the laugh, but there's nothing worth believing in it, this guy doesn't know what he's talking about.
More information at Real World Tech (Score:4, Interesting)
http://www.realworldtech.com/forums/index.cfm?act
Re:Speculations (Score:3, Informative)
Re:Speculations (Score:5, Informative)
It was an add-on specifically designed for the pattern of usage that video cards perform - lots of data out, and short requests in.
It was a patch to get us by until the "next PCI" came along - but AGP's great performance was also the reason it's taken so long to get PCI Express going; not a lot of demand for something we don't really need. Old PCI slots still provide ample bandwidth for most other types of expansion cards and on the server side you had 64-bit PCI/PCI-X.
Of course, we still needed PCIe, but it hasn't been a big push. Now, with the dual-video board thing happening, it's definitely helped push the bus into the mainstream.
As far as the changes in CPU slots, well, I agree to a point. While I believe that both Intel and AMD could have done more to keep slot changes to a minimum, a lot of times the chip-set changes along with the CPU requiring a new board anyways. So, why not upgrade the CPU slot to accommodate the new data patterns of the new architecture?
I do feel like I own hardware. Software, on the other hand..
Re:Speculations (Score:3, Informative)
Re:New low for slashdot (Score:2)
Re:huh (Score:2)
Re:Not the reason for the Apple switch (Score:3, Insightful)
Yes, of course! Why didn't I think of that? Apple moved from a chip supplied by a member of the Trusted Computing Platform Alliance (TCPA) to a chip manufactured by a member of the TCPA because they wanted a chip that supported TCPA! It makes perfect sense.