From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Christoph Hellwig <hch@lst.de>, dledford@redhat.com
Cc: swise@opengridcomputing.com, sagi@grimberg.me,
linux-rdma@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH 09/11] IB/srpt: convert to the generic RDMA READ/WRITE API
Date: Tue, 3 May 2016 14:16:08 -0700 [thread overview]
Message-ID: <57291518.7050508@sandisk.com> (raw)
In-Reply-To: <1462291273-22403-10-git-send-email-hch@lst.de>
On 05/03/2016 09:01 AM, Christoph Hellwig wrote:
> Replace the homegrown RDMA READ/WRITE code in srpt with the generic API.
> The only real twist here is that we need to allocate one Linux scatterlist
> per direct buffer in the SRP command, and chain them before handing them
> off to the target core.
>
> As a side-effect of the conversion the driver will also chain the SEND
> of the SRP response to the RDMA WRITE WRs for a DATA OUT command, and
> properly account for RDMA WRITE WRs instead of just for RDMA READ WRs
> like the driver previously did.
>
> We now allocate half of the SQ size to RDMA READ/WRITE contexts, assuming
> by default one RDMA READ or WRITE operation per command. If a command
> has multiple operations it will eat into the budget but will still succeed,
> possible after waiting for WQEs to be available.
>
> Also ensure the QPs request the maximum allowed SGEs so that RDMA R/W API
> works correctly.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Bart Van Assche <bart.vanassche@sandisk.com>
next prev parent reply other threads:[~2016-05-03 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 16:01 generic RDMA READ/WRITE API V8 Christoph Hellwig
2016-05-03 16:01 ` [PATCH 01/11] IB/cma: pass the port number to ib_create_qp Christoph Hellwig
2016-05-03 16:01 ` [PATCH 02/11] IB/core: allow passing mapping an offset into the SG in ib_map_mr_sg Christoph Hellwig
[not found] ` <1462291273-22403-3-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-05-08 8:08 ` Christoph Hellwig
2016-05-03 16:01 ` [PATCH 03/11] IB/core: add a helper to check for READ WITH INVALIDATE support Christoph Hellwig
2016-05-03 16:01 ` [PATCH 04/11] IB/core: refactor ib_create_qp Christoph Hellwig
[not found] ` <1462291273-22403-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-05-03 16:01 ` [PATCH 05/11] IB/core: add a simple MR pool Christoph Hellwig
2016-05-03 16:01 ` [PATCH 06/11] IB/core: add a need_inval flag to struct ib_mr Christoph Hellwig
2016-05-03 16:01 ` [PATCH 07/11] IB/core: generic RDMA READ/WRITE API Christoph Hellwig
2016-05-03 16:01 ` [PATCH 08/11] target: enhance and export target_alloc_sgl/target_free_sgl Christoph Hellwig
2016-05-03 16:01 ` [PATCH 09/11] IB/srpt: convert to the generic RDMA READ/WRITE API Christoph Hellwig
2016-05-03 21:16 ` Bart Van Assche [this message]
2016-05-03 16:01 ` [PATCH 10/11] IB/core: add RW API support for signature MRs Christoph Hellwig
2016-05-03 16:01 ` [PATCH 11/11] IB/isert: convert to the generic RDMA READ/WRITE API Christoph Hellwig
[not found] ` <1462291273-22403-12-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-05-04 6:15 ` Leon Romanovsky
2016-05-10 17:26 ` generic RDMA READ/WRITE API V8 Steve Wise
2016-05-10 17:29 ` Bart Van Assche
2016-05-12 18:04 ` Doug Ledford
2016-05-12 18:43 ` Doug Ledford
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=57291518.7050508@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=dledford@redhat.com \
--cc=hch@lst.de \
--cc=linux-rdma@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=swise@opengridcomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.