From: Steve Wise <larrystevenwise@gmail.com>
To: dsahern@gmail.com, leon@kernel.org
Cc: Steve Wise <larrystevenwise@gmail.com>,
stephen@networkplumber.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: [PATCH v2 iproute2-next 0/4] Dynamic rdma link creation
Date: Tue, 26 Mar 2019 14:18:26 -0500 [thread overview]
Message-ID: <cover.1553627811.git.larrystevenwise@gmail.com> (raw)
This series adds rdmatool support for creating/deleting rdma links.
This will be used, mainly, by soft rdma drivers to allow adding/deleting
rdma links over netdev interfaces. It provides the user side for
the following kernel changes merged in linux-5.1.
Changes since v1:
- move error receive checking from rd_sendrecv_msg() to rd_recv_msg().
- Add rd->suppress_errors to allow control over whether errors when
reading a response should be ignored. Namely: resource queries can
get errors like "none found" when querying for resources, and this
error should not be displayed. So on a rd object basis, error
suppression can be controlled.
- Rebased on rdma/for-next UABI (no need to sync rdma_netlink.h now)
- use chains of struct rd_cmd and rd_exec_cmd vs open coding the parsing
for the 'link add' command.
- minor nit resolution
- added .mailmap file. If this is not desired for iproute2, then please
drop the patch.
Changes since RFC:
- add rd_sendrecv_msg() and make use of it in dev_set as well
as the new link commands.
- fixed problems with the man pages
- changed the command line to use "netdev" as the keyword
for the network device, do avoid confused with the ib_device
name.
- got rid of the "type" parameter for link delete. Also pass
down the device index instead of the name, using the common
rd services for validating the device name and fetching the
index.
Thanks,
Steve.
----
Steve Wise (4):
Add .mailmap file
rdma: add helper rd_sendrecv_msg()
rdma: add 'link add/delete' commands
rdma: man page update for link add/delete
.mailmap | 8 +++++
man/man8/rdma-link.8 | 47 +++++++++++++++++++++++++
rdma/dev.c | 2 +-
rdma/link.c | 83 ++++++++++++++++++++++++++++++++++++++++++++
rdma/rdma.h | 4 +++
rdma/res.h | 1 +
rdma/utils.c | 18 ++++++++++
7 files changed, 162 insertions(+), 1 deletion(-)
create mode 100644 .mailmap
--
2.20.1
next reply other threads:[~2019-03-26 19:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 19:18 Steve Wise [this message]
2019-03-26 19:18 ` [PATCH v2 iproute2-next 1/4] Add .mailmap file Steve Wise
2019-04-01 6:29 ` Leon Romanovsky
2019-03-26 19:18 ` [PATCH v2 iproute2-next 2/4] rdma: add helper rd_sendrecv_msg() Steve Wise
2019-04-01 2:06 ` David Ahern
2019-04-03 13:16 ` Steve Wise
2019-04-01 6:29 ` Leon Romanovsky
2019-03-26 19:18 ` [PATCH v2 iproute2-next 3/4] rdma: add 'link add/delete' commands Steve Wise
2019-04-01 6:31 ` Leon Romanovsky
2019-04-01 6:37 ` Leon Romanovsky
2019-04-02 14:33 ` Steve Wise
2019-03-26 19:18 ` [PATCH v2 iproute2-next 4/4] rdma: man page update for link add/delete 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=cover.1553627811.git.larrystevenwise@gmail.com \
--to=larrystevenwise@gmail.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).