From: Steve Wise <swise@opengridcomputing.com>
To: dsahern@gmail.com, leon@kernel.org
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: [PATCH RFC iproute2-next 0/2] RDMA tool provider resource tracking
Date: Mon, 30 Apr 2018 08:01:13 -0700 [thread overview]
Message-ID: <cover.1525100473.git.swise@opengridcomputing.com> (raw)
Hello,
This series enhances the iproute2 rdma tool to include displaying
provider-specific resource attributes. It is the user-space part of
the kernel provider resource tracking series currently under
review [1].
This is an RFC and should not be merged yet. Once [1] is in the
linux-rdma for-next branch (and all reviewing is complete), I'll post
a final version and request merging.
Thanks,
Steve.
[1] https://www.spinics.net/lists/linux-rdma/msg64013.html
Steve Wise (2):
rdma: update rdma_netlink.h to get provider attrs
rdma: print provider resource attributes
rdma/include/uapi/rdma/rdma_netlink.h | 37 ++++++-
rdma/rdma.c | 7 +-
rdma/rdma.h | 11 ++
rdma/res.c | 30 ++----
rdma/utils.c | 194 ++++++++++++++++++++++++++++++++++
5 files changed, 257 insertions(+), 22 deletions(-)
--
1.8.3.1
next reply other threads:[~2018-04-30 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 15:01 Steve Wise [this message]
2018-04-30 14:36 ` [PATCH RFC iproute2-next 1/2] rdma: update rdma_netlink.h to get provider attrs Steve Wise
2018-05-02 15:17 ` David Ahern
2018-04-30 14:36 ` [PATCH RFC iproute2-next 2/2] rdma: print provider resource attributes Steve Wise
2018-04-30 15:25 ` Stephen Hemminger
2018-05-02 13:38 ` Leon Romanovsky
2018-05-02 14:32 ` Stephen Hemminger
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.1525100473.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).