On 1/30/07, Sean Hefty [EMAIL PROTECTED] wrote:
I believe that this patch lets you can do what you're trying to do. The group
handle would be the returned mgid from the initial join that created the
group.
The mgid would need to be passed to other processes as an IPv6 address, who
issue a
Or Gerlitz wrote:
Sean,
I understand that your approach relies on the uniqueness of the MGID
being generated. This means that to have different MPI jobs use
different MGIDs , the MGIDs must be generated --always-- on the same
NODE and be propagated to other nodes/ranks participating in that
I understand that your approach relies on the uniqueness of the MGID
being generated. This means that to have different MPI jobs use
different MGIDs , the MGIDs must be generated --always-- on the same
NODE and be propagated to other nodes/ranks participating in that MPI
job - correct?
MGID
Sean Hefty wrote:
I believe that this patch lets you can do what you're trying to do. The
group handle would be the returned mgid from the initial join that
created the group. The mgid would need to be passed to other processes
as an IPv6 address, who issue a join request on that group.
Excellent -- is this in a git tree somewhere that I can grab (I'm new to
git)? Or, what would be an appropriate tree to apply this to?
This is now available from my rdma-dev.git tree on openfabrics. The patch is
included in the multicast and ofed_1_2 branches.
- Sean
Excellent -- is this in a git tree somewhere that I can grab (I'm new to
git)? Or, what would be an appropriate tree to apply this to?
I've committed changes to the librdmacm multicast test program (mckey) that
provides an example of using this functionality. The changes are in the
Sean Hefty wrote:
I've committed changes to the librdmacm multicast test program (mckey) that
provides an example of using this functionality. The changes are in the
librdmacm.git tree master branch.
Great, thanks for working on this! Definitely a newbie here -- I'm
seeing the patches and
Quoting Sean Hefty [EMAIL PROTECTED]:
Subject: Re: [RFC][PATCH] rdma_cm: allow joins to return a unique address
Excellent -- is this in a git tree somewhere that I can grab (I'm new to
git)? Or, what would be an appropriate tree to apply this to?
This is now available from my
Modify rdma_join_multicast to allow the user to specify that
they want the underlying transport to assign them a unique
multicast address. This is done by specifying an IP address
of 0, which will translate into an IB MGID of 0.
To allow others to join this group, we need a way to determine
if
Sean Hefty wrote:
Modify rdma_join_multicast to allow the user to specify that
they want the underlying transport to assign them a unique
multicast address. This is done by specifying an IP address
of 0, which will translate into an IB MGID of 0.
To allow others to join this group, we need
To allow others to join this group, we need a way to determine
if additional join requests are for a specific MGID, or require
IP to MGID mapping. This is done by comparing the requested
join address against SA assigned MGIDs.
Still not understanding this part -- this means that I'm not able
11 matches
Mail list logo
