Generic code MUST support both IPv4 and IPv6 addresses. I've even seen code that actually does this.
So supporting GIDs is not that much of an issue as long as no IB network IDs are assigned with a meaning that conflicts with any reachable IPv6 network ID. (In other words, assign GIDs so that they are in fact valid IPv6 addresses. Something that was always planned to be one option for GIDs). > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of James Lentini > Sent: Thursday, August 25, 2005 9:48 AM > To: Tom Tucker > Cc: [email protected] > Subject: RE: [openib-general] RDMA connection and address > translation API > > > > On Wed, 24 Aug 2005, Tom Tucker wrote: > > > > > > > - It's not just preventing connections to the wrong > local address. > > > NFS-RDMA wants the remote source address (ie > getpeername()) so that > > > it can look it up in the exports list. > > > > Agreed. But you could also get rid of ATS by allowing GIDs to be > > specified in the exports file and then treating them like > > IPv6 addresses for the purpose of subnet comparisons. > > Could generic code use both GIDs and IPv4 addresses? > _______________________________________________ > openib-general mailing list > [email protected] > http://openib.org/mailman/listinfo/openib-general > > To unsubscribe, please visit > http://openib.org/mailman/listinfo/openib-general > > _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
