From: David Ahern <dsahern@gmail.com>
To: Steve Wise <swise@opengridcomputing.com>
Cc: leon@kernel.org, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH v4 iproute2-next 0/7] cm_id, cq, mr, and pd resource tracking
Date: Sun, 1 Apr 2018 09:22:14 -0600 [thread overview]
Message-ID: <8cdcb764-da42-e540-90e6-309eda0eb599@gmail.com> (raw)
In-Reply-To: <cover.1522359537.git.swise@opengridcomputing.com>
On 3/29/18 3:38 PM, Steve Wise wrote:
> 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]
> and [2].
>
> Changes since v3:
> - replaced rdma_cma.h inclusion with UAPI rdma_user_cm.h
> - display only device names instead of device/port for cq, mr, and pd
> since they are not associated with a specific port.
>
> Changes since v2:
> - pull in rdma-core:include/rdma/rdma_cma.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
> [2] https://www.spinics.net/lists/linux-rdma/msg62979.html
> https://www.spinics.net/lists/linux-rdma/msg62980.html
>
> ---
>
applied to iproute2-next. Thanks,
next prev parent reply other threads:[~2018-04-01 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 21:38 [PATCH v4 iproute2-next 0/7] cm_id, cq, mr, and pd resource tracking Steve Wise
2018-03-29 16:10 ` [PATCH v4 iproute2-next 1/7] rdma: update rdma_netlink.h Steve Wise
2018-04-01 10:47 ` Leon Romanovsky
2018-03-29 16:10 ` [PATCH v4 iproute2-next 2/7] rdma: add UAPI rdma_user_cm.h Steve Wise
2018-03-29 16:10 ` [PATCH v4 iproute2-next 3/7] rdma: initialize the rd struct Steve Wise
2018-03-29 16:10 ` [PATCH v4 iproute2-next 4/7] rdma: Add CM_ID resource tracking information Steve Wise
2018-03-29 16:10 ` [PATCH v4 iproute2-next 5/7] rdma: Add CQ " Steve Wise
2018-03-29 16:10 ` [PATCH v4 iproute2-next 6/7] rdma: Add MR " Steve Wise
2018-03-29 16:10 ` [PATCH v4 iproute2-next 7/7] rdma: Add PD " Steve Wise
2018-04-01 15:22 ` David Ahern [this message]
2018-04-01 18:29 ` [PATCH v4 iproute2-next 0/7] cm_id, cq, mr, and pd resource tracking Leon Romanovsky
2018-04-02 1:13 ` 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=8cdcb764-da42-e540-90e6-309eda0eb599@gmail.com \
--to=dsahern@gmail.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=swise@opengridcomputing.com \
/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).