<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Dec 20, 2017, at 6:21 PM, Philip Kovacs <<a href="mailto:pkdevel@yahoo.com" class="">pkdevel@yahoo.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div class=""><div style="background-color: rgb(255, 255, 255); font-family: "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif; font-size: 13px;" class=""><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5702" class="">> -- slurm.spec: move libpmi to a separate package to solve a conflict with the<br id="yui_3_16_0_ym19_1_1513820402811_5703" class=""></div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5704" class="">> version provided by PMIx. This will require a separate change to PMIx as<br id="yui_3_16_0_ym19_1_1513820402811_5705" class=""></div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">> well.</div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class=""><br class=""></div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">I see the intention behind this change since the pmix 2.0+ package provides libpmi/libpmi2</div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">and there is a possible (installation) conflict with the Slurm implementation of those libraries. </div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">We've discussed that issue earlier.</div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class=""><br class=""></div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">Now, suppose a user installs the pmix versions of libpmi/pmi2 with the expectation that pmi</div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">calls will be forwarded to libpmix for greater speed, the so-called "backward compatibility" feature.</div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class=""><br class=""></div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">Shouldn't the Slurm mpi_pmi2 plugin attempt to link with libpmi2 instead of its internal </div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">implementation of pmi2? As it stands now, there won't be any forwarding of pmi2 code </div><div dir="ltr" style="font-family: "Helvetica Neue", "Segoe UI", Helvetica, Arial, "Lucida Grande", sans-serif;" id="yui_3_16_0_ym19_1_1513820402811_5706" class="">to libpmix which I imagine users would expect in that scenario.</div></div></div></div></blockquote></div><br class=""><div class="">Sadly, it isn’t quite that simple. Most of the standard PMI2 calls are covered by the backward compatibility libraries, so things like MPICH should work out-of-the-box.</div><div class=""><br class=""></div><div class="">However, MVAPICH2 added a PMI2 extension call to the SLURM PMI2 library that they use and PMIx doesn’t cover (as there really isn’t an easy equivalent, and they called it PMIX_foo which causes a naming conflict), and so they would not work.</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>