Euro MPI 2015 has returned to Europe! (recall that Euro MPI/Asia 2014 was in beautiful Kyoto, Japan) Euro MPI 2015 will be September 21-24 in Bordeaux, France. That means that it’s that time of year again: get your papers ready for submission
Yesterday morning, I gave a presentation at the 2015 OpenFabrics Software Developers’ Workshop. I discussed the status of libfabric support in Open MPI. Here’s a copy of my slides:
Earlier this morning, I gave a presentation at the 2015 OpenFabrics Software Developers’ Workshop. I discussed Cisco’s experiences with writing providers for both the Linux Verbs API and the Libfabric API. Here’s a copy of my slides:
The MPI Forum met for our quarterly meeting last week in Portland, Oregon. The main goal of the meeting was to pass the MPI-3.1 standard into law. MPI-3.1 contains a bunch of errata from MPI-3.0, and a small number of new things.
With a little sadness, I note that LAM/MPI was officially retired recently. LAM/MPI’s hosting provider, Indiana University, made the decision not to renew the lam-mpi.org domain any more. As of a few weeks ago, LAM/MPI’s web site is no
Working on an MPI implementation isn’t always sexy. There’s a lot of grubby, grubby work that needs to happen on a continual basis to produce a production-quality MPI implementation that can be used for real-world HPC applications. Sure
The next MPI Forum meeting will be in Portland, OR, USA, in early March. One of the major topics on the agenda will be voting on the MPI 3.1 standard. You might be wondering what’s new in MPI-3.1. I’m glad you asked.
In my prior blog entry, I described the basics of Open MPI’s tree-based launching system over ssh (yes, there are still some valid / good reasons for using ssh over a native job scheduler / resource manager’s parallel launch
I’ve mentioned it before: the run-time systems of MPI implementations are frequently unsung heroes. A lot of blood, sweat, tears, and innovation goes into parallel run time systems, particularly those that can scale to very large systems. But