Hey Doug/Jason, Do you plan to merge this for 4.17? If so I need to sync rdma_netlink.h in iproute-next, once you pull it in. Thanks, Steve. On 3/30/2018 1:05 PM, Steve Wise wrote: > This series adds new resource tracking attributes and APIs for > rdma providers to add their own implementation specific attributes. > Included in this series is the core changes, and a cxgb4-specific QP > implementation. > > Changes since v2: > - remove cb from provider fill API functions > - null out function pointers explicitly > - remove BIN print type > - provide unspec and hex helpers, and only the ones needed for this > submission > - rebased on to rdma-next > > Changes since v1: > - refactor provider attr code to remove X32/X64 attributes. > - add helper functions for filling out provider attributes > - make use of helpers in cxgb4/restrack.c > - add Reviewed-by tag. > > Changes since v0/rfc: > - removed RFC tag > - add PAD attribute while preserving the ABI > - remove "provider_" prefix from restrack_root fn ptr names. > - enable link and dev provider-specific attributes. > - fixed copyright dates on cxgb4/restack.c. > > > Steve Wise (5): > RDMA/nldev: Add explicit pad attribute > RDMA/nldev: add provider-specific resource tracking > RDMA/nldev: add provider-specific device/port tracking > RDMA/NLDEV: helper functions to add provider attributes > iw_cxgb4: dump detailed provider-specific QP information > > drivers/infiniband/core/nldev.c | 154 +++++++++++++++-- > drivers/infiniband/core/restrack.c | 3 + > drivers/infiniband/hw/cxgb4/Makefile | 3 +- > drivers/infiniband/hw/cxgb4/iw_cxgb4.h | 5 + > drivers/infiniband/hw/cxgb4/provider.c | 8 + > drivers/infiniband/hw/cxgb4/restrack.c | 294 +++++++++++++++++++++++++++++++++ > include/rdma/restrack.h | 36 ++++ > include/uapi/rdma/rdma_netlink.h | 23 +++ > 8 files changed, 512 insertions(+), 14 deletions(-) > create mode 100644 drivers/infiniband/hw/cxgb4/restrack.c > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
