Showing posts with label multicore. Show all posts
Showing posts with label multicore. Show all posts

Wednesday, May 21, 2008

Intel HexaCore Dunnington at 2.66Ghz

Intel has taped out its six-core processor running at 2.66Ghz, which it plans to release sometime in Q4 2008. Intel's six-core processor is currently codenamed Xeon Dunnington has 3 dual-core processors stuck with each other and run as a single packaged processor. The processor will require a new socket to run. But the good news is that Intel is able to extract good speeds from it.

Dunnington is a reply to AMD's 3-core processors (TriCore), which AMD had initially thought to be value-for-money for the customers. Intel on the other hand has no plans to sell Dunnington's for cheap and will be sold only as server processors, under the Xeon brand. The Dunnington processors have a huge cache of 16MB, which should be very attractive for applications that run a lot of threads. Another news has it that, Dunnington will be running a single thread per core, and does not use HyperThreading (HT) technology.

The last time I met an Intel Design Engineer from Bangalore, I had heard that Intel was much impressed by Sun's designs in Rock or Niagara 2. Lots of concurrent threads on a core are very good on servers. Intel seems to going forward with the core-race at the moment, but I expect a switch to more threads on a core very soon!!

Friday, November 30, 2007

Complete Nehalem Details Leaked

True to the earlier reports about Intel's next chips having HT (Hyper-Threading) and integrated-GPU, some more details about Nehalem appeared on the web, courtesy of Japan's PC Watch.

image image

The architecture diagrams mention about 2 threads per core, which was what I had heard from James Reinders earlier. The PCWatch page also has pictures of the updated Intel roadmaps. It also has features of all the different variations of Nehalem that Intel is going to release. The code names of these are Beckton (Oct-core MP), Gainestown (Quad-core DP), Bloomfield (Quad-core, EE-Desktop), Lynnfield (Mainstream Quad-core) and Havendale (Mainstream Dualcore)

Beckton Gainestown Bloomfield Lynnfield Havendale

If you can understand Japanese, then go here and read all about it or use a translator and try to figure out what it means!!

Wednesday, October 24, 2007

Intel Wants Developers To Program For MultiCore

Intel Organizes Seminar On Multi-Core Programming In Mumbai

I have just come back from an Intel Software Seminar Series held in Mumbai at Leela. Intel organized this seminar for developers, so that they could make a paradigm shift towards programming for Multi-Core processors. India is a major hub of software developers and Intel thinks they need to help programmers make the shift!!

A while back I had read this article on "Multi-Core Crisis" and found it as an interesting representation. Today, at the seminar, the first speaker, Vivek Venkatesh showed few slides on why there is a need for multi-core processors and how the future is going to be multi-core processors. How Intel plans to move by increasing the number of cores in the future. He made a statement that, "Youtube and multimedia require multi-core processors"... Im wondering how I watch youtube videos on my single core AthlonXP machine?? :-)) He also stressed on, "the free lunch is over" statement made by Herb Sutter.

Free Image Hosting at www.ImageShack.us Free Image Hosting at www.ImageShack.us

After the session was over, the Q&A session started and I put a question of how RapidMind would help realize this goal. James Reinders dismissed RapidMind's innovation as being too tough to implement in the current state, but mentioned that the idea has some promise!!

Next to come on stage, James Reinders was the main speaker at the Seminar. James has been working with Intel for 19yrs and he has been a multi-core evangelist for sometime now! It was great listening to his insights and made some very interesting points on what software developers and architects need to think when programming multi-core computers.

James mentioned 1-2-3 recommendations that developers can do today to use multi-core processors:
1.) Libraries - James mentioned that use of libraries that are written for multi-core processors are like putting your burden on someone else's shoulders.
2.) openMP - Intel was one of the main contributor to this standard and nearly every C/C++ compiler today uses it. James recommends using modern compilers like MS C Compiler and gcc that use openMP
3.) Threading Building Blocks (TBB) - This is Intel's new software to help multi-core programming by providing abstraction. James said this is an opensource software and should be used by developers who want to program. He showed example codes of how hand-made optimization for multi-core processors to Tacheon (2-D Ray Tracing) was complex and in just 17 lines of code using TBB, the work can be reduced.

He also mentioned challenges for multi-core programming:
1.) Scalability
2.) Correctness
3.) Maintainability

At the end, he talked about the 8-points that any developer must follow for multi-core programming. James wrote this for a Dr. Dobb's Journal, in the October edition. Read here...

In the concluding part before lunch, we had a quiz contest and I won a personally autographed book named "Intel - Threading Building Blocks" from James Reinders.

I also asked James Reinders about HT and Nehalem, since I knew he was one of the minds at Intel who supported Hyper-Threading (HT). He told that Core architecture wasn't benefiting much from HT and hence HT wasn't added to Core. But he told that Nehalem would be with HT enabled and would be processing 2 threads in each core. He also said that in the future Intel may go through Sun's Niagara 2 path of more threads per core, atleast in the server space.

Overall it was a nice insight into what's happening at Intel and what Intel feels about multi-core programming.

Other Photos from the event (2 other colleagues: Mandar & Namrata also attended):
Free Image Hosting at www.ImageShack.us Free Image Hosting at www.ImageShack.us