Announcement

Collapse
No announcement yet.

Intel Pushes Their Linux-Friendly Xeon Phi

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • F i L
    replied
    Originally posted by Cyborg16 View Post
    Also Parallella is MIMD whereas the Phi (according to WP) and GPUs are SIMD, so Parallella is more general (surprisingly).
    I've always thought that was more future proof, really. I'm no engineer, but it makes sense to sacrifice chip complexity for scalability. Plus, it's probably easier to write/compile against. No special SIMD instructions or significant architectural changes from chip to chip (theoretically). Just simple cores at different amounts.

    Leave a comment:


  • ChrisXY
    replied
    Originally posted by Figueiredo View Post
    I remember that some years ago intel was touting ray-traycing as the future of graphics, this card should probably be very good a it. Is there any open source ray-traycing engine?
    There were several tech demos with the predecessor of knights corner, knights ferry, the last two being quake wars and wolfenstein:




    I haven't seen a download for the code so you probably can't get it for free...

    Leave a comment:


  • ldesnogu
    replied
    Originally posted by chuckula View Post
    The vector units in the Xeon Phi are using the same instruction format as the AVX instructions found in Sandy Bridge/Ivy Bridge chips that are already on the market. The Xeon Phi's extend the SIMD instruction length to 512 bits, but otherwise it is the same format (this was done intentionally, and AVX actually scales all the way up to 1024 bit SIMD instructions).
    I think you are wrong: on top of being wider there are now 32 registers instead of 16. Instruction encoding also is different and there are new instructions. So definitely something completely new

    Leave a comment:


  • chuckula
    replied
    Originally posted by ldesnogu View Post
    gcc doesn't really have support for Xeon Phi since it doesn't support their new SIMD extension. Intel just needed to be able to compile the kernel. If you want a compiler, you'll have to use icc.

    The vector units in the Xeon Phi are using the same instruction format as the AVX instructions found in Sandy Bridge/Ivy Bridge chips that are already on the market. The Xeon Phi's extend the SIMD instruction length to 512 bits, but otherwise it is the same format (this was done intentionally, and AVX actually scales all the way up to 1024 bit SIMD instructions).

    The bigger isssue with Xeon Phi is actually that the cores are simplified x86 meaning they drop some legacy instructions. That's not the end of the world but it does mean that GCC and the kernel need some tweaking so that they are only issuing valid instructions. To get the best performance out of these chips, your workload should be dominated by the SIMD instructions, which is what compute bound tasks are all about.

    Leave a comment:


  • Cyborg16
    replied
    Originally posted by F i L View Post
    I wounder how the Xeon Phi compares to Adapteva's 64-core Parallella processor.
    Parallella's a lot cheaper, and probably also slower due to simpler die. Also Parallella is MIMD whereas the Phi (according to WP) and GPUs are SIMD, so Parallella is more general (surprisingly).

    Leave a comment:


  • ldesnogu
    replied
    gcc doesn't really have support for Xeon Phi since it doesn't support their new SIMD extension. Intel just needed to be able to compile the kernel. If you want a compiler, you'll have to use icc.

    Leave a comment:


  • F i L
    replied
    Originally posted by Figueiredo View Post
    Is there any open source ray-traycing engine?
    IDK, but here to hoping the Atomontage Engine gets adapted to this (and ported to Linux?). Voxels, in theory, are more suited to ray-tracing than polygonal objects.

    Leave a comment:


  • zxy_thf
    replied
    Originally posted by Figueiredo View Post
    They have probably (and intelligently) decided that it would be easier to start with a HPC part, since the margins in this market allow for a very big and expensive die, and evolve it to eventually serve the graphics industry also. This may also be good for linux, since HPC requires good linux support.

    I remember that some years ago intel was touting ray-traycing as the future of graphics, this card should probably be very good a it. Is there any open source ray-traycing engine?

    Looking forward, this part should be fairly interesting, as it will surelly shake things up a bit due to the ease of programability and linux friendliness.
    Lightsmark adopts global illumination algorithm, but I don't know it's ray-tracing or not.
    Maybe the simplest way is; wait patiently for another 10-15 years till id tech 6 becomes open-source.

    Leave a comment:


  • F i L
    replied
    I wounder how the Xeon Phi compares to Adapteva's 64-core Parallella processor.

    Leave a comment:


  • Figueiredo
    replied
    They have probably (and intelligently) decided that it would be easier to start with a HPC part, since the margins in this market allow for a very big and expensive die, and evolve it to eventually serve the graphics industry also. This may also be good for linux, since HPC requires good linux support.

    I remember that some years ago intel was touting ray-traycing as the future of graphics, this card should probably be very good a it. Is there any open source ray-traycing engine?

    Looking forward, this part should be fairly interesting, as it will surelly shake things up a bit due to the ease of programability and linux friendliness.

    Leave a comment:

Working...
X