netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jason Gunthorpe <jgg@mellanox.com>,
	RDMA mailing list <linux-rdma@vger.kernel.org>,
	Guy Levi <guyle@mellanox.com>,
	Yonatan Cohen <yonatanc@mellanox.com>,
	Saeed Mahameed <saeedm@mellanox.com>,
	linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next v1 0/4] Scatter to CQE
Date: Wed, 17 Oct 2018 11:27:41 -0400	[thread overview]
Message-ID: <f21a7543b35a9aa764cb7ba65c219819668b6baf.camel@redhat.com> (raw)
In-Reply-To: <20181016190008.GL3606@mtr-leonro.mtl.com>

[-- Attachment #1: Type: text/plain, Size: 2584 bytes --]

On Tue, 2018-10-16 at 22:00 +0300, Leon Romanovsky wrote:
> On Tue, Oct 16, 2018 at 02:39:01PM -0400, Doug Ledford wrote:
> > On Tue, 2018-10-09 at 12:05 +0300, Leon Romanovsky wrote:
> > > From: Leon Romanovsky <leonro@mellanox.com>
> > > 
> > > Changelog v0->v1:
> > >  * Changed patch #3 to use check_mask function from rdma-core instead define.
> > > 
> > > --------------------------------------------------------------------------
> > > From Yonatan,
> > > 
> > > Scatter to CQE is a HW offload feature that saves PCI writes by
> > > scattering the payload to the CQE.
> > > 
> > > The feature depends on the CQE size and if the CQE size is 64B, it will
> > > work for payload smaller than 32. If the CQE size is 128B, it will work for
> > > payload smaller than 64.
> > > 
> > > The feature works for responder and requestor:
> > > 1. For responder, if the payload is small as required above, the data
> > > will be part of the CQE, and thus we save another PCI transaction the recv buffers.
> > > 2. For requestor, this can be used to get the RDMA_READ response and
> > > RDMA_ATOMIC response in the CQE. This feature is already supported in upstream.
> > > 
> > > As part of this series, we are adding support for DC transport type and
> > > ability to enable the feature (force enable) in the requestor when SQ
> > > is not configured to signal all WRs.
> > > 
> > > Thanks
> > > 
> > > Yonatan Cohen (4):
> > >   net/mlx5: Expose DC scatter to CQE capability bit
> > >   IB/mlx5: Support scatter to CQE for DC transport type
> > >   IB/mlx5: Verify that driver supports user flags
> > >   IB/mlx5: Allow scatter to CQE without global signaled WRs
> > > 
> > >  drivers/infiniband/hw/mlx5/cq.c      |  2 +-
> > >  drivers/infiniband/hw/mlx5/mlx5_ib.h |  2 +-
> > >  drivers/infiniband/hw/mlx5/qp.c      | 93 ++++++++++++++++++++++++++++--------
> > >  include/linux/mlx5/mlx5_ifc.h        |  3 +-
> > >  include/uapi/rdma/mlx5-abi.h         |  1 +
> > >  5 files changed, 79 insertions(+), 22 deletions(-)
> > > 
> > > --
> > > 2.14.4
> > > 
> > 
> > 
> > Hi Leon,
> > 
> > This series looks fine.  Let me know when the net/mlx5 portion has been
> > committed.
> 
> Thanks Doug,
> I pushed first patch to mlx5-next
> 94a04d1d3d36 ("net/mlx5: Expose DC scatter to CQE capability bit")

Thanks Leon, mlx5-next merged in, then remainder of series applied to
for-next.

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-10-17 23:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09  9:05 [PATCH rdma-next v1 0/4] Scatter to CQE Leon Romanovsky
2018-10-09  9:05 ` [PATCH mlx5-next v1 1/4] net/mlx5: Expose DC scatter to CQE capability bit Leon Romanovsky
2018-10-09  9:05 ` [PATCH rdma-next v1 2/4] IB/mlx5: Support scatter to CQE for DC transport type Leon Romanovsky
2018-10-09  9:05 ` [PATCH rdma-next v1 3/4] IB/mlx5: Verify that driver supports user flags Leon Romanovsky
2018-10-09  9:05 ` [PATCH rdma-next v1 4/4] IB/mlx5: Allow scatter to CQE without global signaled WRs Leon Romanovsky
2018-10-16 18:39 ` [PATCH rdma-next v1 0/4] Scatter to CQE Doug Ledford
2018-10-16 19:00   ` Leon Romanovsky
2018-10-17 15:27     ` Doug Ledford [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=f21a7543b35a9aa764cb7ba65c219819668b6baf.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=guyle@mellanox.com \
    --cc=jgg@mellanox.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.com \
    --cc=yonatanc@mellanox.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 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).