Why not just use IP to MAC calls? Or use the MAC as the GUID?
We do use standard OS services to map the IP addresses (that were
encoded in the GID) to MACs.
GIDs encode IP addresses rather than MACs to enable users to use the
node names that they are used to.
Specifically, we will feed in all
Hum, This is a very tricky subject. Co-mingling the IB GID address
space and the IPv6 address space like this is not really something
that was envisioned from the IBA side.
Doesn't the IB spec say that an IB GID *is* an IPv6 address? So in
theory it should be OK; however I don't think in
On Wed, Jun 17, 2009 at 11:20:26AM -0700, Roland Dreier wrote:
Hum, This is a very tricky subject. Co-mingling the IB GID address
space and the IPv6 address space like this is not really something
that was envisioned from the IBA side.
Doesn't the IB spec say that an IB GID *is* an
It is like an IPv6 address but it was expressly envisioned to be a
seperate space. The IBA authors copied many of the conventions from
IPv6 for numbering this new space, like link local, and multicast
prefixes, but it was not intended to be co-mingled.
Well (I've quoted this many times):
On Wed, Jun 17, 2009 at 11:38:43AM -0700, Roland Dreier wrote:
It is like an IPv6 address but it was expressly envisioned to be a
seperate space. The IBA authors copied many of the conventions from
IPv6 for numbering this new space, like link local, and multicast
prefixes, but it was
Hmm, murky indeed. Your point about IGMPv6 is well made. The problem
is that IB GRHs are not IPv6 headers and have different numerology for
the Next Header field. Ie in IPv6 Next Header 0x1B is RFC 908, while
in GRH it is a BTH. Labeling GRHs with an IPv6 ethertype is
fundamentally
A few support functions are added to allow the translation from GID to MAC
which is required by hw drivers supporting RDMAoE.
Why not just use IP to MAC calls? Or use the MAC as the GUID?
Do the GIDs follow the IB GID format?
___
ewg mailing list
