From: Leon Romanovsky <leon@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Leon Romanovsky <leonro@nvidia.com>, Ido Kalir <idok@nvidia.com>,
linux-netdev <netdev@vger.kernel.org>,
Mark Zhang <markz@mellanox.com>,
Neta Ostrovsky <netao@nvidia.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: [PATCH iproute2-next 0/3] Add context and SRQ information to rdmatool
Date: Sun, 25 Apr 2021 14:53:19 +0300 [thread overview]
Message-ID: <cover.1619351025.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Hi,
This is the user space part of already accepted to the kernel series
that extends RDMA netlink interface to return uverbs context and SRQ
information.
The accepted kernel series can be seen here:
https://lore.kernel.org/linux-rdma/20210422133459.GA2390260@nvidia.com/
Thanks
Neta Ostrovsky (2):
rdma: Update uapi headers
rdma: Add context resource tracking information
rdma: Add SRQ resource tracking information
man/man8/rdma-resource.8 | 12 +-
rdma/Makefile | 2 +-
rdma/include/uapi/rdma/rdma_netlink.h | 13 ++
rdma/res-ctx.c | 103 ++++++++++
rdma/res-srq.c | 274 ++++++++++++++++++++++++++
rdma/res.c | 8 +-
rdma/res.h | 28 +++
rdma/utils.c | 8 +
8 files changed, 445 insertions(+), 3 deletions(-)
create mode 100644 rdma/res-ctx.c
create mode 100644 rdma/res-srq.c
--
2.30.2
next reply other threads:[~2021-04-25 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 11:53 Leon Romanovsky [this message]
2021-04-25 11:53 ` [PATCH iproute2-next 1/3] rdma: Update uapi headers Leon Romanovsky
2021-04-25 11:53 ` [PATCH iproute2-next 2/3] rdma: Add context resource tracking information Leon Romanovsky
2021-04-25 11:53 ` [PATCH iproute2-next 3/3] rdma: Add SRQ " Leon Romanovsky
2021-04-28 15:38 ` [PATCH iproute2-next 0/3] Add context and SRQ information to rdmatool David Ahern
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.1619351025.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=dsahern@gmail.com \
--cc=idok@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=markz@mellanox.com \
--cc=netao@nvidia.com \
--cc=netdev@vger.kernel.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).