Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Konstantin Taranov <konstantin.taranov@inf.ethz.ch>
Cc: monis@mellanox.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] Make rxe driver to calculate correct byte_len on receiving side when work completion is generated with IB_WC_RECV_RDMA_WITH_IMM opcode.
Date: Mon, 8 Jul 2019 16:51:20 -0300	[thread overview]
Message-ID: <20190708195120.GA25113@ziepe.ca> (raw)
In-Reply-To: <20190627140643.6191-1-konstantin.taranov@inf.ethz.ch>

On Thu, Jun 27, 2019 at 04:06:43PM +0200, Konstantin Taranov wrote:
> Make softRoce to calculate correct byte_len on receiving side when work completion
> is generated with IB_WC_RECV_RDMA_WITH_IMM opcode.
> 
> According to documentation byte_len must indicate the number of written
> bytes, whereas it was always equal to zero for IB_WC_RECV_RDMA_WITH_IMM opcode.
> 
> The patch proposes to remember the length of an RDMA request from the RETH header, and use it 
> as byte_len when the work completion with IB_WC_RECV_RDMA_WITH_IMM opcode is generated.
> 
> Signed-off-by: Konstantin Taranov <konstantin.taranov@inf.ethz.ch>
> ---
>  drivers/infiniband/sw/rxe/rxe_resp.c  | 5 ++++-
>  drivers/infiniband/sw/rxe/rxe_verbs.h | 1 +
>  2 files changed, 5 insertions(+), 1 deletion(-)

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2019-07-08 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190627140643.6191-1-konstantin.taranov@inf.ethz.ch>
     [not found] ` <d149da15-523a-438a-1550-095b4b1a840b@oracle.com>
2019-07-07 21:23   ` [PATCH] Make rxe driver to calculate correct byte_len on receiving side when work completion is generated with IB_WC_RECV_RDMA_WITH_IMM opcode Konstantin Taranov
2019-07-07 23:35     ` Zhu Yanjun
2019-07-08  1:46       ` Konstantin Taranov
2019-07-08  1:57         ` Yanjun Zhu
2019-07-08 19:51 ` 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=20190708195120.GA25113@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=konstantin.taranov@inf.ethz.ch \
    --cc=linux-rdma@vger.kernel.org \
    --cc=monis@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