From: Jason Gunthorpe <jgg@nvidia.com>
To: Vitaly Mayatskikh <vitaly@enfabrica.net>
Cc: Leon Romanovsky <leon@kernel.org>,
Shiraz Saleem <shiraz.saleem@intel.com>,
linux-rdma@vger.kernel.org, David Ahern <dsahern@kernel.org>,
Roland Dreier <roland@enfabrica.net>
Subject: Re: [PATCH] RDMA/core: use rdma_cap_iw_cm() in rdma_resolve_route()
Date: Wed, 20 Sep 2023 10:55:41 -0300 [thread overview]
Message-ID: <20230920135541.GA13733@nvidia.com> (raw)
In-Reply-To: <CAF0WxhnXDfXE94O7etK8edWGiA+b4D792sNzz8b7w7H7D_=kvQ@mail.gmail.com>
On Wed, Sep 20, 2023 at 09:53:00AM -0400, Vitaly Mayatskikh wrote:
> On Wed, Sep 20, 2023 at 9:10 AM Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> > But is it iWarp?
> >
> > I'm not keen on seeing people abuse iwarp stuff for some non-standards
> > based thing. iwarp is already in a disused state, there isn't enough
> > community energy there to police something non-standards based.
>
> No, it is IP-based, but not iWarp. Using CM implementation for
> IP-network (IW_CM) was a logical decision. In fact, IW_CM can be
> rebranded as IP_CM as it is not tightly coupled with iWarp per se and
> can serve any IP-based protocols.
And what happens if one of your non-standard nodes points its IWCM at
an IP that is actually running iWarp?
Jason
next prev parent reply other threads:[~2023-09-20 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 14:27 [PATCH] RDMA/core: use rdma_cap_iw_cm() in rdma_resolve_route() Vitaly Mayatskikh
2023-09-19 7:21 ` Leon Romanovsky
[not found] ` <CAF0Wxh=YhKCLbOLZ+-b+_rmzRoWQtqoBGn6Bo9X3zR308Vm1zA@mail.gmail.com>
2023-09-19 20:08 ` Vitaly Mayatskikh
2023-09-20 5:44 ` Leon Romanovsky
2023-09-20 12:55 ` Jason Gunthorpe
2023-09-20 13:07 ` Vitaly Mayatskikh
2023-09-20 13:10 ` Jason Gunthorpe
2023-09-20 13:53 ` Vitaly Mayatskikh
2023-09-20 13:55 ` Jason Gunthorpe [this message]
2023-09-20 14:24 ` Vitaly Mayatskikh
2023-09-20 16:02 ` Jason Gunthorpe
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=20230920135541.GA13733@nvidia.com \
--to=jgg@nvidia.com \
--cc=dsahern@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=roland@enfabrica.net \
--cc=shiraz.saleem@intel.com \
--cc=vitaly@enfabrica.net \
/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