[Mpi-forum] ticket 273

Richard Graham richardg at mellanox.com
Wed May 30 15:03:50 CDT 2012

  Two items that I wrote down based on comments:
 - One view was expressed that adding a nonblocking interface, will not change the fact that implementation will still be blocking
- The ticket was rushed, and not ready


-----Original Message-----
From: mpi-forum-bounces at lists.mpi-forum.org [mailto:mpi-forum-bounces at lists.mpi-forum.org] On Behalf Of Mohamad Chaarawi
Sent: Thursday, May 31, 2012 4:37 AM
To: Main MPI Forum mailing list
Subject: [Mpi-forum] ticket 273

Hi All,

I'm still trying to figure out why ticket 273 was voted down. At the last meeting, I would say there was a consensus that the non blocking collective I/O ticket (273) was ready to be voted in. Nobody expressed an objection after me removing the shared file pointer nbc routines and re-reading the draft. All the I/O chapter committee reviewed the draft and commented on the ticket that it looks good.

At the Japan meeting, we get 8 yes , 2 nos, and 6 abstains, which under the new rules marks the ticket as failed.
None from our organization could attend the meeting to really understand what the 2 no votes were for, and why 6 organizations abstained.
If the abstains are because people don't care or don't understand what is being voted on or missed the vote (which are the reasons why I vote abstain), then the new voting rule doesn't really make sense. If the abstains where for something else, then the votes should be NO. So could someone mention why this was voted down?


mpi-forum mailing list
mpi-forum at lists.mpi-forum.org

More information about the mpi-forum mailing list