Slashdot Mirror


A Co-processor No More, Intel's Xeon Phi Will Be Its Own CPU As Well

An anonymous reader writes "The Xeon Phi co-processor requires a Xeon CPU to operate... for now. The next generation of Xeon Phi, codenamed Knights Landing and due in 2015, will be its own CPU and accelerator. This will free up a lot of space in the server but more important, it eliminates the buses between CPU memory and co-processor memory, which will translate to much faster performance even before we get to chip improvements. ITworld has a look."

9 of 53 comments (clear)

  1. Re:CPU embedded in GPU versus GPU embedded in CPU by Overzeetop · · Score: 4, Funny

    Patents already cover most implementations of GPUs within CPUs. But the field is wide open if you start embedding CPUs in GPUs. It's like "on the internet," but with uprocessors.

    --
    Is it just my observation, or are there way too many stupid people in the world?
  2. Optionally by Sockatume · · Score: 2

    Knights Landing will be available as both an accelerator card and a standalone CPU with some sort of large high-speed memory pool on the die.

    --
    No kidding!!! What do you say at this point?
  3. Fully Baked? by DragonDru · · Score: 4, Informative

    Good. The current generation Phi cards are a pain to administer. With luck the new generation will be more fully baked.
    - very hot card, no fans
    - depends on software to down throttle the cards (mine have hit 104C)
    - stripped down OS running on the cards, poor user facing directions for the usage

    Anyway, enough from me.

    --
    20 characters max for the password? How will I use my favorite poems as passwords?
    1. Re:Fully Baked? by Junta · · Score: 5, Informative

      I won't disagree about the awkwardness of MPSS, but the 'very hot card, no fans' is because it's meant only to be installed into systems that cooperate with them and have cooling designs where the hosting system takes care of it. For a lot of systems that Phi go into, a fan is actually a liability because those systems already have cooling solutions and a fan actually fights with the designed airflow.

      Of course, that's why nVidia offers up two Tesla variants of every model, one with and one without fan, to cater to both worlds.

      --
      XML is like violence. If it doesn't solve the problem, use more.
  4. Re:CPU embedded in GPU versus GPU embedded in CPU by Anonymous Coward · · Score: 2, Interesting

    It's not just for drawing graphics. It can be used as a general computation platform.

    As an example imagemagick supports OpenCL nowadays. So as an example if you have a webpage where images can be uploaded and you do some processing for them (cropping, scaling for thumbnails etc) you can get absolutely amazing performance on a server with GPU.

  5. Frankly, the accelerator card is pretty dumb by Anonymous Coward · · Score: 3, Interesting

    For a Phi, the selling point is about ease of programming. The memory model of the accelerator card is a pain in the ass, making development more difficult. This on top of the fact that the administration of those are pretty limited and annoying. MPSS is crap for everyone, and one of the critical differences here is that the standalone accelerator might not require Intel to be the linux distribution curator anymore (they frankly suck pretty hard at it).

    Intel having a standalone variant pretty much obviates the utility of an accelerator card model for all but perhaps the tiniest usage and makes things far more simpler. Trying to get the same workload to work across Phi and main CPUs is, in practice, more about trying to make the best of an awkward heterogeneous compute situation. While you still can and will run jobs heterogeneous if you do have both Phi and normal Xeon nodes (e.g. a top500 run and... well not much else), it is done using more typical methods of MPI.

    In short, this move pretty much let's intel focus on the pieces they *are* good at (making a decent processor) and get away from the stuff they aren't so good at (pcie hosted device, linux distribution design, etc).

  6. 80487 coprocessor all over? by Anonymous Coward · · Score: 5, Interesting

    The 80486 was the first Intel processor with integrated coprocessor, coming at about €1000 (only know the DM price). There was a considerably cheaper version, the 80486SX "without" coprocessor (actually, the coprocessor was usually just disabled, possibly because of yield problems, and still took current).

    One could buy an 80487 coprocessor that provided the missing floating point performance. Customers puzzled how the processor/coprocessor combination could be competitive without the on-chip communication of the 80486. The answer was that it did not even try. The "coprocessor" contained a CPU as well and simply switched off the "main" processor completely. It was basically a full 80486 with different pinout, pricing, and marketing.

    It was probably phased out once the yields became good enough.

  7. Re:Yee-haw no more by Sockatume · · Score: 2

    If you're going to nitpick, at least act like you want to educate people and aren't just being a smartass:

    1) It's a law the same way Newton's Laws are laws: it's a simple quantitative relation which has held up very well over time.

    2) a) In its original formulation it said that the number of components you could put on a chip at minimum cost (because you can always cram in more at higher cost) doubled ever year.

    ii) In its later correction (he used only five data points in the first paper!) he revised this to every two years.

    gamma) It was a head honcho in Intel who then concluded that such a relationship would double overall computer performance every eighteen months.

    Given that the components of interest on a processor are transistors, I do not have any great objection to the generalisation that it's transistor counts that double and not all components.

    --
    No kidding!!! What do you say at this point?
  8. i see a problem with this by etash · · Score: 2

    wouldn't an embedded in the cpu xeon phi version, lack the necessary GDDR4/5 which exists in the PCI-express card version with its 200-300GB/s of throughput, and be forced to just access the main computer RAM at about 40-50GB/s?