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: RE: [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking
Date: Mon, 12 Mar 2018 10:16:32 -0500 [thread overview]
Message-ID: <0b9901d3ba15$1ac4a1d0$504de570$@opengridcomputing.com> (raw)
In-Reply-To: <cover.1520020530.git.swise@opengridcomputing.com>
Hey all,
The kernel side of this series has been merged for rdma-next [1]. Let me
know if this iproute2 series can be merged, of if it needs more changes.
Thanks,
Steve.
[1] https://www.spinics.net/lists/linux-rdma/msg61720.html
> -----Original Message-----
> From: linux-rdma-owner@vger•kernel.org [mailto:linux-rdma-
> owner@vger•kernel.org] On Behalf Of Steve Wise
> Sent: Friday, March 02, 2018 1:56 PM
> To: dsahern@gmail•com
> Cc: leon@kernel•org; stephen@networkplumber•org; netdev@vger•kernel.org;
> linux-rdma@vger•kernel.org
> Subject: [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource
tracking
>
> 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 resource tracking series under review now on the linux-rdma list [1].
>
> 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/msg61400.html
>
> Thanks,
>
> Steve.
> ---
>
> Steve Wise (6):
> 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 +
> include/uapi/rdma/rdma_netlink.h | 44 ++-
> lib/json_writer.c | 11 +
> rdma/rdma.c | 2 +-
> rdma/rdma.h | 2 +
> rdma/res.c | 611
++++++++++++++++++++++++++++++++++++++-
> rdma/utils.c | 16 +
> 7 files changed, 683 insertions(+), 5 deletions(-)
>
> --
> 1.8.3.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-03-12 15:16 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 19:55 [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking Steve Wise
2018-02-27 16:06 ` [PATCH v2 iproute2-next 1/6] rdma: update rdma_netlink.h Steve Wise
2018-02-27 16:07 ` [PATCH v2 iproute2-next 2/6] rdma: initialize the rd struct Steve Wise
2018-03-13 18:11 ` Leon Romanovsky
2018-02-27 16:07 ` [PATCH v2 iproute2-next 3/6] rdma: Add CM_ID resource tracking information Steve Wise
2018-03-13 18:07 ` Leon Romanovsky
2018-03-13 19:44 ` Steve Wise
2018-03-26 14:17 ` David Ahern
2018-03-26 14:30 ` Steve Wise
2018-03-26 14:44 ` David Ahern
2018-03-26 14:55 ` Steve Wise
2018-03-26 15:08 ` Leon Romanovsky
2018-03-26 15:24 ` Steve Wise
2018-03-26 17:06 ` Leon Romanovsky
2018-03-26 17:13 ` Steve Wise
2018-03-26 17:27 ` Leon Romanovsky
2018-03-26 21:15 ` Jason Gunthorpe
2018-03-26 21:34 ` Steve Wise
2018-03-26 22:30 ` Jason Gunthorpe
2018-03-27 3:21 ` Leon Romanovsky
2018-03-27 14:44 ` Jason Gunthorpe
2018-03-27 15:15 ` Leon Romanovsky
2018-03-27 15:23 ` Jason Gunthorpe
2018-03-27 15:45 ` Steve Wise
2018-03-27 16:01 ` Leon Romanovsky
2018-03-27 16:20 ` Steve Wise
2018-03-27 16:30 ` Leon Romanovsky
2018-03-27 16:38 ` Steve Wise
2018-03-26 15:40 ` David Ahern
2018-03-26 19:55 ` Steve Wise
2018-02-27 16:07 ` [PATCH v2 iproute2-next 4/6] rdma: Add CQ " Steve Wise
2018-03-13 19:05 ` Leon Romanovsky
2018-02-27 16:07 ` [PATCH v2 iproute2-next 5/6] rdma: Add MR " Steve Wise
2018-03-13 19:06 ` Leon Romanovsky
2018-02-27 16:07 ` [PATCH v2 iproute2-next 6/6] rdma: Add PD " Steve Wise
2018-03-13 19:07 ` Leon Romanovsky
2018-03-12 15:16 ` Steve Wise [this message]
2018-03-12 17:53 ` [PATCH v2 iproute2-next 0/6] cm_id, cq, mr, and pd resource tracking David Ahern
2018-03-12 18:43 ` Steve Wise
2018-03-13 8:32 ` Leon Romanovsky
2018-03-13 20:45 ` David Ahern
2018-03-13 20:58 ` Doug Ledford
2018-03-16 16:18 ` David Ahern
2018-03-20 17:21 ` Doug Ledford
2018-03-21 16:59 ` David Ahern
2018-03-22 20:20 ` Steve Wise
2018-03-22 20:26 ` David Ahern
2018-03-13 21:13 ` Jason Gunthorpe
2018-03-15 3:14 ` David Ahern
2018-03-15 3:29 ` Jason Gunthorpe
2018-03-16 16:08 ` David Ahern
2018-03-16 16:23 ` Leon Romanovsky
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='0b9901d3ba15$1ac4a1d0$504de570$@opengridcomputing.com' \
--to=swise@opengridcomputing$(echo .)com \
--cc=dsahern@gmail$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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