A blog of interesting technical advances.
February 11, 2010
The HPC Stack
I was reading the news today and came across this article. The author believse that there should be no seperation between cluster level message passing and hardware acceleration. Furthermore, he believes that application writers should only have to use one API to an entire cluster with specialized hardware. I would think that the best way to accomplish this is to use a hybrid approach where a specific API is used for cluster messaging and another API is used for hardware acceleration. This seperation is mostly beneficial from a project management standpoint as it can reduce the scope of the message passing interface and the hardware accelerator considerably and allows the projects to be run completely independent. Yes, a programmer would have to learn two API's instead of one, but accelerating a program using hardware would have a different API from message passing no matter the abstraction. Therefore, adding an API on top of this would still have almost the same number of calls as the number of calls in each library added together.
Subscribe to:
Post Comments (Atom)
Archives
- June 2013 (1)
- October 2012 (1)
- March 2012 (1)
- May 2011 (2)
- September 2010 (1)
- April 2010 (1)
- February 2010 (4)
- January 2010 (5)
Me
- Spenser Gilliland
- Waco, Texas, United States
Electrical and Computer with an interest in FPGAs, Linux, and Embedded Systems. Enjoys playing with servers and experimenting with virtualization.
No comments:
Post a Comment