From: David Ahern <dsahern@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Leon Romanovsky <leonro@mellanox.com>,
netdev <netdev@vger.kernel.org>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2-next v1 00/19] Export object IDs to users
Date: Thu, 21 Feb 2019 10:26:44 -0500 [thread overview]
Message-ID: <b2a33de0-eb68-fdc8-934f-d75c3ebb1927@gmail.com> (raw)
In-Reply-To: <20190220072136.3840-1-leon@kernel.org>
On 2/20/19 2:21 AM, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> Changelog:
> v0->v1:
> * Rebased to latest iproute2-next
> * Added latest rdma_netlink.h and updated commit message to point
> to kernel SHA commit.
>
> This series adds ability to present and query all known to rdmatool
> object by their respective, unique IDs (e.g. pdn. mrn, cqn e.t.c).
> All objects which have "parent" object has this information too.
>
> Thanks
>
I would prefer someone from the rdma world review this as well. Thanks
prev parent reply other threads:[~2019-02-21 15:26 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 7:21 [PATCH iproute2-next v1 00/19] Export object IDs to users Leon Romanovsky
2019-02-20 7:21 ` [PATCH iproute2-next v1 01/19] rdma: update uapi headers Leon Romanovsky
2019-02-21 20:02 ` Steve Wise
2019-02-21 22:11 ` Leon Romanovsky
2019-02-20 7:21 ` [PATCH iproute2-next v1 02/19] rdma: Remove duplicated print code Leon Romanovsky
2019-02-21 15:23 ` David Ahern
2019-02-21 15:39 ` Leon Romanovsky
2019-02-21 20:04 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 03/19] rdma: Provide unique indexes for all visible objects Leon Romanovsky
2019-02-21 20:08 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 04/19] rdma: Provide parent context index for all objects except CM_ID Leon Romanovsky
2019-02-21 20:12 ` Steve Wise
2019-02-23 9:03 ` Leon Romanovsky
2019-02-20 7:21 ` [PATCH iproute2-next v1 05/19] rdma: Move resource PD logic to separate file Leon Romanovsky
2019-02-21 20:15 ` Steve Wise
2019-02-23 9:05 ` Leon Romanovsky
2019-02-20 7:21 ` [PATCH iproute2-next v1 06/19] rdma: Refactor out resource MR " Leon Romanovsky
2019-02-21 20:15 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 07/19] rdma: Move out resource CQ " Leon Romanovsky
2019-02-21 20:16 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 08/19] rdma: Move out resource CM-ID " Leon Romanovsky
2019-02-21 20:17 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 09/19] rdma: Move resource PD " Leon Romanovsky
2019-02-21 20:21 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 10/19] rdma: Properly mark RDMAtool license Leon Romanovsky
2019-02-21 20:22 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 11/19] rdma: Simplify code to reuse existing functions Leon Romanovsky
2019-02-21 20:23 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 12/19] rdma: Simplify CM_ID print code Leon Romanovsky
2019-02-21 20:26 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 13/19] rdma: Refactor CQ prints Leon Romanovsky
2019-02-21 20:27 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 14/19] rdma: Separate MR code Leon Romanovsky
2019-02-21 20:28 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 15/19] rdma: Separate PD code Leon Romanovsky
2019-02-21 20:29 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 16/19] rdma: Move QP code to separate function Leon Romanovsky
2019-02-21 20:29 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 17/19] rdma: Unify netlink attribute checks prior to prints Leon Romanovsky
2019-02-21 20:31 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 18/19] rdma: Perform single .doit call to query specific objects Leon Romanovsky
2019-02-21 20:35 ` Steve Wise
2019-02-20 7:21 ` [PATCH iproute2-next v1 19/19] rdma: Provide and reuse filter functions Leon Romanovsky
2019-02-21 20:39 ` Steve Wise
2019-02-21 15:26 ` David Ahern [this message]
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=b2a33de0-eb68-fdc8-934f-d75c3ebb1927@gmail.com \
--to=dsahern@gmail.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--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).