From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bart.vanassche@sandisk.com>
Cc: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] ib_srp: initialize dma_length in srp_map_idb
Date: Sun, 15 Nov 2015 20:20:51 +0200 [thread overview]
Message-ID: <5648CD03.4000206@dev.mellanox.co.il> (raw)
In-Reply-To: <1447610393-2899-1-git-send-email-hch@lst.de>
On 15/11/2015 19:59, Christoph Hellwig wrote:
> Without this sg_dma_len will return 0 on architectures tha have
> the dma_length field.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/infiniband/ulp/srp/ib_srp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/infiniband/ulp/srp/ib_srp.c b/drivers/infiniband/ulp/srp/ib_srp.c
> index 32f7962..445c0a6 100644
> --- a/drivers/infiniband/ulp/srp/ib_srp.c
> +++ b/drivers/infiniband/ulp/srp/ib_srp.c
> @@ -1520,6 +1520,9 @@ static int srp_map_idb(struct srp_rdma_ch *ch, struct srp_request *req,
> state.sg_nents = 1;
> sg_set_buf(idb_sg, req->indirect_desc, idb_len);
> idb_sg->dma_address = req->indirect_dma_addr; /* hack! */
> +#ifdef CONFIG_NEED_SG_DMA_LENGTH
> + idb_sg->dma_length = idb_sg->length; /* hack^2 */
> +#endif
:)
We should really get this properly map/unmap per IO at some point.
Probably do it in both code paths...
Having said that,
Looks fine,
Reviewed-by: Sagi Grimberg <sagig@mellanox.com>
next prev parent reply other threads:[~2015-11-15 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 17:59 [PATCH] ib_srp: initialize dma_length in srp_map_idb Christoph Hellwig
2015-11-15 18:20 ` Sagi Grimberg [this message]
[not found] ` <5648CD03.4000206-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-11-15 21:10 ` Or Gerlitz
2015-11-16 9:50 ` Sagi Grimberg
[not found] ` <1447610393-2899-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-11-16 17:16 ` Bart Van Assche
2015-11-16 17:22 ` Christoph Hellwig
2015-11-16 17:52 ` Bart Van Assche
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=5648CD03.4000206@dev.mellanox.co.il \
--to=sagig@dev.mellanox.co.il \
--cc=bart.vanassche@sandisk.com \
--cc=hch@lst.de \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@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.