On 11/02/2013 20:02, Hefty, Sean wrote:
Define AF_IB and sockaddr_ib to allow the rdma_cm to use native IB addressing.
Signed-off-by: Sean Hefty <[email protected]>
---
include/linux/socket.h | 2 +
include/rdma/ib.h | 89 ++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 91 insertions(+), 0 deletions(-)
create mode 100644 include/rdma/ib.h
diff --git a/include/linux/socket.h b/include/linux/socket.h
index 9a546ff..17a33f7 100644
--- a/include/linux/socket.h
+++ b/include/linux/socket.h
@@ -167,6 +167,7 @@ struct ucred {
#define AF_PPPOX 24 /* PPPoX sockets */
#define AF_WANPIPE 25 /* Wanpipe API Sockets */
#define AF_LLC 26 /* Linux LLC */
+#define AF_IB 27 /* Native InfiniBand address */
...
diff --git a/include/rdma/ib.h b/include/rdma/ib.h
...
+struct sockaddr_ib {
+ unsigned short int sib_family; /* AF_IB */
+ __be16 sib_pkey;
+ __be32 sib_flowinfo;
+ struct ib_addr sib_addr;
+ __be64 sib_sid;
+ __be64 sib_sid_mask;
+ __u64 sib_scope_id;
+};
Dave/Roland/anyone, is there any feedback on this approach?
If there's hesitation to add new address families to socket.h, I could instead
use definitions local to the rdma_cm. This has the potential to result in
conflicts if the rdma_cm is expanded for other address families, though such
conflicts seem unlikely.
I don't see why not add new address family if it comes to serve a real
world use case, which seems to be the case from the description you
provided in the cover letter.
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
