From: Steve Wise <swise@opengridcomputing.com>
To: dsahern@gmail.com
Cc: leon@kernel.org, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: [PATCH v3 iproute2-next 0/8] cm_id, cq, mr, and pd resource tracking
Date: Mon, 26 Mar 2018 13:59:51 -0700 [thread overview]
Message-ID: <cover.1522097991.git.swise@opengridcomputing.com> (raw)
Hello,
This series enhances the iproute2 rdma tool to include dumping of
connection manager id (cm_id), completion queue (cq), memory region (mr),
and protection domain (pd) rdma resources. It is the user-space part
of the kernel resource tracking series merged into rdma-next for 4.17 [1].
Changes since v2:
- pull in rdma-core include/rdma/rdma_cma.h
- update the new local rdma/include/uapi/rdma/rdma_netlink.h
- 80 column reformat
- add reviewed-by tags
Changes since v1/RFC:
- removed RFC tag
- initialize rd properly to avoid passing a garbage port number
- revert accidental change to qp_valid_filters
- removed cm_id dev/network/transport types
- cm_id ip addrs now passed up as __kernel_sockaddr_storage
- cm_id ip address ports printed as "address:port" strings
- only parse/display memory keys and iova if available
- filter on "users" for cqs and pds
- fixed memory leaks
- removed PD_FLAGS attribute
- filter on "mrlen" for mrs
- filter on "poll-ctx" for cqs
- don't require addrs or qp_type for parsing cm_ids
- only filter optional attrs if they are present
- remove PGSIZE MR attr to match kernel
[1] https://www.spinics.net/lists/linux-rdma/msg61720.html
---
Steve Wise (8):
rdma: include rdma-core <rdma/rdma_cma.h>
rdma: Makefile change to find <rdma/rdma_cma.h>
rdma: update rdma_netlink.h
rdma: initialize the rd struct
rdma: Add CM_ID resource tracking information
rdma: Add CQ resource tracking information
rdma: Add MR resource tracking information
rdma: Add PD resource tracking information
include/json_writer.h | 2 +
lib/json_writer.c | 11 +
rdma/Makefile | 2 +-
rdma/include/rdma/rdma_cma.h | 728 ++++++++++++++++++++++++++++++++++
rdma/include/uapi/rdma/rdma_netlink.h | 38 ++
rdma/rdma.c | 2 +-
rdma/rdma.h | 2 +
rdma/res.c | 623 ++++++++++++++++++++++++++++-
rdma/utils.c | 16 +
9 files changed, 1421 insertions(+), 3 deletions(-)
create mode 100644 rdma/include/rdma/rdma_cma.h
--
1.8.3.1
next reply other threads:[~2018-03-26 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 20:59 Steve Wise [this message]
2018-03-26 20:57 ` [PATCH v3 iproute2-next 1/8] rdma: include rdma-core <rdma/rdma_cma.h> Steve Wise
2018-03-27 5:46 ` Leon Romanovsky
2018-03-27 13:23 ` David Ahern
2018-03-26 20:57 ` [PATCH v3 iproute2-next 2/8] rdma: Makefile change to find <rdma/rdma_cma.h> Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 3/8] rdma: update rdma_netlink.h Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 4/8] rdma: initialize the rd struct Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 5/8] rdma: Add CM_ID resource tracking information Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 6/8] rdma: Add CQ " Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 7/8] rdma: Add MR " Steve Wise
2018-03-26 20:57 ` [PATCH v3 iproute2-next 8/8] rdma: Add PD " Steve Wise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1522097991.git.swise@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=dsahern@gmail.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).