From: Chuck Lever <cel@kernel.org>
To: netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Cc: BMT@zurich.ibm.com, tom@talpey.com
Subject: [PATCH RFC 0/3] siw on tunnel devices
Date: Fri, 05 May 2023 11:41:50 -0400 [thread overview]
Message-ID: <168330051600.5953.11366152375575299483.stgit@oracle-102.nfsv4bat.org> (raw)
Chalk this one up to yet another crazy idea.
At NFS testing events, we'd like to test NFS/RDMA over the event's
private network. We can do that with iWARP using siw from guests.
If the guest itself is on the VPN, that means siw's slave device
is a tun device. Such devices have no MAC address. That breaks the
RDMA core's ability to find the correct egress device for siw when
given a source IP address.
We've worked around this in the past with various software hacks,
but we'd rather see full support for this capability in stock
kernels.
A direct and perhaps naïve way to do that is to give loopback and
tun devices their own artificial MAC addresses for this purpose.
---
Chuck Lever (3):
net/tun: Ensure tun devices have a MAC address
net/lo: Ensure lo devices have a MAC address
RDMA/siw: Require non-zero 6-byte MACs for soft iWARP
drivers/infiniband/sw/siw/siw_main.c | 22 +++++++---------------
drivers/net/loopback.c | 2 ++
drivers/net/tun.c | 6 +++---
3 files changed, 12 insertions(+), 18 deletions(-)
--
Chuck Lever
next reply other threads:[~2023-05-05 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 15:41 Chuck Lever [this message]
2023-05-05 15:42 ` [PATCH RFC 1/3] net/tun: Ensure tun devices have a MAC address Chuck Lever
2023-05-05 16:59 ` Stephen Hemminger
2023-05-05 17:09 ` Chuck Lever III
2023-05-05 15:42 ` [PATCH RFC 2/3] net/lo: Ensure lo " Chuck Lever
2023-05-05 16:57 ` Stephen Hemminger
2023-05-05 15:43 ` [PATCH RFC 3/3] RDMA/siw: Require non-zero 6-byte MACs for soft iWARP Chuck Lever
2023-05-05 19:58 ` Jason Gunthorpe
2023-05-05 20:03 ` Chuck Lever III
2023-05-06 18:05 ` Chuck Lever III
2023-05-23 19:18 ` Chuck Lever III
2023-05-23 19:44 ` Tom Talpey
2023-05-23 22:50 ` Chuck Lever III
2023-05-31 19:04 ` Jason Gunthorpe
2023-05-31 19:11 ` Chuck Lever III
2023-05-31 20:09 ` Jason Gunthorpe
2023-05-31 20:19 ` Chuck Lever III
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=168330051600.5953.11366152375575299483.stgit@oracle-102.nfsv4bat.org \
--to=cel@kernel.org \
--cc=BMT@zurich.ibm.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tom@talpey.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.