public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
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:10:32 -0300	[thread overview]
Message-ID: <20230920131032.GY13733@nvidia.com> (raw)
In-Reply-To: <CAF0WxhkuN0J3K5tUw0rb3-v=zKPKTh5YcCGSciaBXx9yfN-GEw@mail.gmail.com>

On Wed, Sep 20, 2023 at 09:07:44AM -0400, Vitaly Mayatskikh wrote:
> On Wed, Sep 20, 2023 at 8:55 AM Jason Gunthorpe <jgg@nvidia.com> wrote:
> 
> > > > > Our driver does not support iWarp, but implements IW_CM callbacks. The patch has
> > > > > the only fix that was needed to make it work w/o a full blown iWarp.
> > >
> > > It is hard to say without having driver in-tree and seeing the result of
> > > ib_device_check_mandatory() in regards of kverbs_provider variable.
> > >
> > > Does any existing in-tree driver require the proposed change in
> > > rdma-cm?
> >
> > Yes, lets see a driver first please.
> >
> > iWarp CM is tightly tied to iWarp, I have a hard time understanding
> > how you could have the CM without supporting iWarp too.
> 
> Yes, it is coming. Not sure about the timeline, but the intent is to
> opensource the drivers. I'll defer the patch till then.
> 
> The IB driver implements ib_device_ops->iw_* ops and cq/qp/mr-related
> kverbs. This is sufficient for CM to work with the device in
> principle.

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.

Jason

  reply	other threads:[~2023-09-20 13:10 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 [this message]
2023-09-20 13:53               ` Vitaly Mayatskikh
2023-09-20 13:55                 ` Jason Gunthorpe
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=20230920131032.GY13733@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