1456d97c01
Creating a UD address handle from user-space or from the kernel-space, when the link layer is ethernet, requires resolving the remote L3 address into a L2 address. Doing this from the kernel is easy because the required ARP(IPv4) and ND6(IPv6) address resolving APIs are readily available. In userspace such an interface does not exist and kernel help is required. It should be noted that in an IP-based GID environment, the GID itself does not contain all the information needed to resolve the destination IP address. For example information like VLAN ID and SCOPE ID, is not part of the GID and must be fetched from the GID attributes. Therefore a source GID should always be referred to as a GID index. Instead of going through various racy steps to obtain information about the GID attributes from user-space, this is now all done by the kernel. This patch optimises the L3 to L2 address resolving using the existing create address handle uverbs interface, retrieving back the L2 address as an additional user-space information structure. This commit combines the following Linux upstream commits: IB/core: Let create_ah return extended response to user IB/core: Change ib_resolve_eth_dmac to use it in create AH IB/mlx5: Make create/destroy_ah available to userspace IB/mlx5: Use kernel driver to help userspace create ah IB/mlx5: Report that device has udata response in create_ah MFC after: 1 week Sponsored by: Mellanox Technologies |
||
---|---|---|
.. | ||
common | ||
crypto | ||
cudbg | ||
cxgbei | ||
firmware | ||
iw_cxgbe | ||
tom | ||
adapter.h | ||
if_cc.c | ||
if_ccv.c | ||
if_cxl.c | ||
if_cxlv.c | ||
offload.h | ||
osdep.h | ||
t4_if.m | ||
t4_ioctl.h | ||
t4_iov.c | ||
t4_l2t.c | ||
t4_l2t.h | ||
t4_main.c | ||
t4_mp_ring.c | ||
t4_mp_ring.h | ||
t4_netmap.c | ||
t4_sched.c | ||
t4_sge.c | ||
t4_tracer.c | ||
t4_vf.c |