From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@mellanox.com>,
Bart Van Assche <bvanassche@acm.org>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
Christoph Hellwig <hch@lst.de>,
Danil Kipnis <danil.kipnis@cloud.ionos.com>,
"David S. Miller" <davem@davemloft.net>,
Jack Wang <jinpu.wang@cloud.ionos.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
rds-devel@oss.oracle.com, Sagi Grimberg <sagi@grimberg.me>,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
target-devel@vger.kernel.org
Subject: Re: [PATCH rdma-next v3 0/6] Add Enhanced Connection Established (ECE)
Date: Wed, 27 May 2020 16:14:24 -0300 [thread overview]
Message-ID: <20200527191424.GA20778@ziepe.ca> (raw)
In-Reply-To: <20200526103304.196371-1-leon@kernel.org>
On Tue, May 26, 2020 at 01:32:58PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> Changelog:
> v3:
> * Rebased on top of ebd6e96b33a2 RDMA/ipoib: Remove can_sleep parameter from iboib_mcast_alloc
> * Updated rdma_reject patch to include newly added RTR ulp
> * Remove empty hunks added by rebase
> * Changed signature of rdma_reject so kernel users will provide reason by themselves
> * Squashed UAPI patch to other patches which add functionality
> * Removed define of the IBTA reason from UAPI
> v2: https://lore.kernel.org/linux-rdma/20200413141538.935574-1-leon@kernel.org/
> * Rebased on latest rdma-next and removed already accepted patches.
> * Updated all rdma_reject in-kernel users to provide reject reason.
> v1: Dropped field_avail patch in favor of mass conversion to use function
> which already exists in the kernel code.
> https://lore.kernel.org/lkml/20200310091438.248429-1-leon@kernel.org
> v0: https://lore.kernel.org/lkml/20200305150105.207959-1-leon@kernel.org
>
> Enhanced Connection Established or ECE is new negotiation scheme
> introduced in IBTA v1.4 to exchange extra information about nodes
> capabilities and later negotiate them at the connection establishment
> phase.
>
> The RDMA-CM messages (REQ, REP, SIDR_REQ and SIDR_REP) were extended
> to carry two fields, one new and another gained new functionality:
> * VendorID is a new field that indicates that common subset of vendor
> option bits are supported as indicated by that VendorID.
> * AttributeModifier already exists, but overloaded to indicate which
> vendor options are supported by this VendorID.
>
> This is kernel part of such functionality which is responsible to get data
> from librdmacm and properly create and handle RDMA-CM messages.
>
> Thanks
>
> Leon Romanovsky (6):
> RDMA/cm: Add Enhanced Connection Establishment (ECE) bits
> RDMA/ucma: Extend ucma_connect to receive ECE parameters
> RDMA/ucma: Deliver ECE parameters through UCMA events
> RDMA/cm: Send and receive ECE parameter over the wire
> RDMA/cma: Connect ECE to rdma_accept
> RDMA/cma: Provide ECE reject reason
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2020-05-27 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 10:32 [PATCH rdma-next v3 0/6] Add Enhanced Connection Established (ECE) Leon Romanovsky
2020-05-27 19:14 ` Jason Gunthorpe [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=20200527191424.GA20778@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bvanassche@acm.org \
--cc=chaitanya.kulkarni@wdc.com \
--cc=danil.kipnis@cloud.ionos.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=hch@lst.de \
--cc=jinpu.wang@cloud.ionos.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=sagi@grimberg.me \
--cc=santosh.shilimkar@oracle.com \
--cc=target-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).