All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Tom Talpey <tom@talpey.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	Benjamin Coddington <bcodding@redhat.com>
Subject: Re: directing soft iWARP traffic through a secure tunnel
Date: Fri, 19 Feb 2021 14:54:43 +0000	[thread overview]
Message-ID: <287F954B-04DC-4EEA-B810-2BCFF9F8C15D@oracle.com> (raw)
In-Reply-To: <OF54DF919C.5715D846-ON00258681.004F4160-00258681.00500D35@notes.na.collabserv.com>



> On Feb 19, 2021, at 9:34 AM, Bernard Metzler <BMT@zurich.ibm.com> wrote:
> 
> -----"Tom Talpey" <tom@talpey.com> wrote: -----
> 
>> To: "Jason Gunthorpe" <jgg@ziepe.ca>, "Bernard Metzler"
>> <BMT@zurich.ibm.com>
>> From: "Tom Talpey" <tom@talpey.com>
>> Date: 02/19/2021 03:15PM
>> Cc: "Chuck Lever" <chuck.lever@oracle.com>, "linux-rdma"
>> <linux-rdma@vger.kernel.org>, "Benjamin Coddington"
>> <bcodding@redhat.com>
>> Subject: [EXTERNAL] Re: directing soft iWARP traffic through a secure
>> tunnel
>> 
>> On 2/19/2021 8:57 AM, Jason Gunthorpe wrote:
>>> 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.
>> 
>> iWarp doesn't really need a CM, it is capable of peer-to-peer without
>> any need to assign connection and queuepair ID's. The CM
>> infrastructure
>> basically just implements a state machine to allow upper layers to
>> have
>> a consistent connection API.
> 
> Well hardware iWarp need someone to organize taking away ports
> from kernel TCP which are bound to RNIC's.
> 
>> 
>> I'm with Bernard here, forcing iWarp to use CM is a fairly unnatural
>> act. Assigning a GID/GUID is unnecessary from a protocol perspective.
>> 
>> 
>>> With Steve gone I don't think there is really anyone left that even
>>> really knows how the iWarp stuff works??
>>> 
> 
> Cleaning up the iWarp path of it might be a complex undertaking.
> I don't think going down that path solves the issue soon enough
> for NFS/RDMA folks.

We have a temporary solution for the upcoming event. There will
be more such events in the future.


> But I will spend some time trying to wrap
> my head around it...
> 
> Best,
> Bernard.

--
Chuck Lever




      reply	other threads:[~2021-02-19 14:55 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
2021-02-19 14:12       ` Tom Talpey
2021-02-19 14:34       ` Bernard Metzler
2021-02-19 14:54         ` Chuck Lever [this message]

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=287F954B-04DC-4EEA-B810-2BCFF9F8C15D@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=BMT@zurich.ibm.com \
    --cc=bcodding@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@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.