From: Jason Gunthorpe <jgg@ziepe.ca>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
linux-rdma <linux-rdma@vger.kernel.org>,
Benjamin Coddington <bcodding@redhat.com>
Subject: Re: Re: directing soft iWARP traffic through a secure tunnel
Date: Fri, 19 Feb 2021 09:57:28 -0400 [thread overview]
Message-ID: <20210219135728.GD2643399@ziepe.ca> (raw)
In-Reply-To: <OF3B04E71D.E72E1A4D-ON00258681.004164EA-00258681.00480051@notes.na.collabserv.com>
On Fri, Feb 19, 2021 at 01:06:26PM +0000, Bernard Metzler wrote:
> Actually, all this GID and GUID and friends for iWARP
> CM looks more like squeezing things into InfiniBand terms,
> where we could just rely on plain ARP and IP
> (ARP resolve interface, see if there is an RDMA device
> bound to, done)... or do I miss something?
I don't know how iWarp cM works very well, it would not be surprising
if the gid table code has gained general rocee behaviors that are not
applicable to iwarp modes.
With Steve gone I don't think there is really anyone left that even
really knows how the iWarp stuff works??
Jason
next prev parent reply other threads:[~2021-02-19 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 19:35 directing soft iWARP traffic through a secure tunnel Chuck Lever
2021-02-12 12:37 ` Bernard Metzler
2021-02-12 13:02 ` Benjamin Coddington
2021-02-12 13:02 ` Chuck Lever
2021-02-12 13:19 ` Bernard Metzler
2021-02-12 13:23 ` Benjamin Coddington
2021-02-12 15:26 ` Bernard Metzler
2021-02-16 12:27 ` Bernard Metzler
2021-02-16 18:09 ` Jason Gunthorpe
2021-02-19 13:06 ` Bernard Metzler
2021-02-19 13:57 ` Jason Gunthorpe [this message]
2021-02-19 14:12 ` Tom Talpey
2021-02-19 14:34 ` Bernard Metzler
2021-02-19 14:54 ` Chuck Lever
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=20210219135728.GD2643399@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=BMT@zurich.ibm.com \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-rdma@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 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.