Originally posted by mateli
View Post
One is the library for traditional OpenGL applications who have no idea about Xeon Phi.
Another is a Xeon Phi application, running in a different process located at a different host, because Xeon Phi is a standalone machine connected with PCI-e bus actually.
A brief TODO list for Xeon Phi rendering:
1. Write a Mesa driver on the host (your core i?, athlon, ppc or any cpu you like)
The driver needs to translate OpenGL commands into some intermediate form messages and pass them to the server running on Xeon Phi.
In other words, the state tracker (gallium) is left on the host.
(Sending OpenGL commands directly is possible, but I'd rather run the state tracker on a superscalar processor)
2. Write a OpenGL server on Xeon Phi
The server needs to parse messages and complete the rendering work.
This server can use llvmpipe, but rewriting from scratch is also possible, esp. for some commerical OpenGL vendors.
It's another story to optimize the OpenGL Sever, but I believe Xeon Phi is the furture for OSS high performance 3D.
Comment