We have talked many times about doing proper versioning for OMPI's .so
libraries (e.g., libmpi.so -- *not* our component DSOs). After
reading up on the Libtool recommendations on how to do this, I have
added a the relevant stuff to the relevant Makefile.am's, and also
added a small conveni
On Jul 23, 2009, at 12:06 , Brian W. Barrett wrote:
On Thu, 23 Jul 2009, Jeff Squyres wrote:
There are two solutions I can think of. Which should we do?
a. Pass the (max?) PML header size down into the BTL during
initialization such that the the btl_XXX_eager_limit can
represent the max MPI
Found it - a simple "<=" instead of "<".
Test compiling now - should be in trunk shortly.
Thanks, oh test pilot!
On Jul 23, 2009, at 11:19 AM, Eugene Loh wrote:
Oh ye gods of rankfiles:
I have a node that has two sockets, each with four cores. If I use
a rankfile, I can bind to a specific
oopsdefinitely looks like a bug to me! I gather you
only have 4 cores on that node?
I'll take a look at it. I assume this is on the trunk?
On Jul 23, 2009, at 11:19 AM, Eugene Loh wrote:
Oh ye gods of rankfiles:
I have a node that has two sockets, each with four cores. If I use
a ra
Oh ye gods of rankfiles:
I have a node that has two sockets, each with four cores. If I use a
rankfile, I can bind to a specific core, a specific range of cores, or a
specific core or range of cores of a specific socket. I'm having
trouble binding to all cores of a specific socket. It's loo
On Thu, 23 Jul 2009, Jeff Squyres wrote:
There are two solutions I can think of. Which should we do?
a. Pass the (max?) PML header size down into the BTL during
initialization such that the the btl_XXX_eager_limit can
represent the max MPI data payload size (i.e., the BTL can siz
I am curious if you are indeed using a new interconnect (new
hardware and protocol) or if it is requirements of the 3D-torus
network that are not addressed by the openib btl that are driving
the need for a new btl?
It is the first one.
Sebastian.
On 07/21/09 11:55, Sebastian Rinke wrot
WHAT: a) Clarify the actual max MPI payload size for eager messages
(i.e., the exact meaning of btl_XXX_eager_limit), and b) allow
network administrators to shape network traffic by publishing
actual BTL max wire fragment sizes (i.e., MPI max payload size +
max PML header s
