Frontiers of Multi­Core Computing workshop CFP

Print Friendly, PDF & Email

Reader Bill Feiereisen emailed in to let us know about the 2nd Workshop on “Frontiers of Multi­Core Computing” (FMC II), coming up at the University of Maryland, Baltimore County, September 22-23, 2010. Details:

Multi‐ (e.g., Intel Nehalm and IBM Power 7) and many‐core (e.g., NVIDIA Tesla and AMD FireStream GPUs) microprocessors are enabling more compute‐ and data‐ intensive computation in desktop computers, clusters, and leadership supercomputers. However efficient utilization of these microprocessors is still a very challenging issue. Their differing architectures require significantly different programming paradigms when adapting real‐world applications. The actual porting costs are actively debated, as well as the relative performance between GPUs and CPUs.

The goal of this workshop is to provide a forum for academic researchers, industrials, and funding agencies to exchange ideas, discuss, and develop the strategies for coping with those challenges.

Topics of interests include (but are not limited to)

  • GPU vs. CPU: performance, porting effort, and productivity
  • Heterogeneous Parallel Programming Paradigms
  • Petaflop Computing and Beyond
  • Data‐Intensive Computing
  • Extreme Environmental Modeling and Simulation
  • Situation Awareness Simulations
  • Web based Computations for Personalized Medicine
  • Social and Eco‐Physics
  • Developments in 3‐D Depth Information
  • Bringing multi/many‐core applications and programming to the “missing middle”

One-page abstracts due Aug 10, 2010; submissions should be sent by email to szhou@umbc.edu with the subject of “FMC II submission ‐ [AuthorName]”.

Comments

  1. JR Rothschild says

    Where can I sign up for this year’s conference? I can’t find a current web page. Thanks.

    • John West says

      JR – me either; I’ve sent an email in, but in the meantime I’d recommend you send an email to the papers chair and see what he says.

  2. Send an email 3 days ago already, no reply yet… Let’s wait some more then.