From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Sagi Grimberg
<sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
infinipath-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
target-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH V4 3/5] RDMA/iser: Limit sg tablesize and max_sectors to device fastreg max depth
Date: Sun, 05 Jul 2015 08:15:05 -0500 [thread overview]
Message-ID: <55992DD9.2010909@opengridcomputing.com> (raw)
In-Reply-To: <5598FFA3.5020508-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
On 7/5/2015 4:57 AM, Sagi Grimberg wrote:
> On 7/2/2015 6:16 PM, Steve Wise wrote:
>> Currently the sg tablesize, which dictates fast register page list
>> depth to use, does not take into account the limits of the rdma device.
>> So adjust it once we discover the device fastreg max depth limit. Also
>> adjust the max_sectors based on the resulting sg tablesize.
>>
>> Signed-off-by: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
>> Reviewed-by: Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>> ---
>> drivers/infiniband/ulp/iser/iscsi_iser.c | 9 +++++++++
>> 1 files changed, 9 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/infiniband/ulp/iser/iscsi_iser.c
>> b/drivers/infiniband/ulp/iser/iscsi_iser.c
>> index 6a594aa..0ed8638 100644
>> --- a/drivers/infiniband/ulp/iser/iscsi_iser.c
>> +++ b/drivers/infiniband/ulp/iser/iscsi_iser.c
>> @@ -640,6 +640,15 @@ iscsi_iser_session_create(struct iscsi_endpoint
>> *ep,
>> SHOST_DIX_GUARD_CRC);
>> }
>>
>> + /*
>> + * Limit the sg_tablesize and max_sectors based on the device
>> + * max fastreg page list length.
>> + */
>> + shost->sg_tablesize = min_t(u32, shost->sg_tablesize,
>> + ib_conn->device->dev_attr.max_fast_reg_page_list_len);
>> + shost->max_sectors =
>> + min(1024, (shost->sg_tablesize * PAGE_SIZE) >> 9);
>> +
>
> Steve,
>
> This triggers a compilation warning:
> drivers/infiniband/ulp/iser/iscsi_iser.c: In function
> iscsi_iser_session_create:
> drivers/infiniband/ulp/iser/iscsi_iser.c:653: warning: comparison of
> distinct pointer types lacks a cast
>
> For next time, let's remove the reviewed-by tags and I'll re-review the
> patches.
Oops. My bad.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-05 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 15:16 [PATCH V4 0/5] iSER support for iWARP Steve Wise
2015-07-02 15:16 ` [PATCH V4 1/5] mlx4, mlx5, mthca: Expose max_sge_rd correctly Steve Wise
2015-07-02 15:16 ` [PATCH V4 4/5] RDMA/isert: Set REMOTE_WRITE on DMA MRs to support iWARP devices Steve Wise
[not found] ` <20150702151508.12946.29133.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2015-07-02 15:16 ` [PATCH V4 2/5] ipath,qib: Expose max_sge_rd correctly Steve Wise
2015-07-02 15:16 ` [PATCH V4 3/5] RDMA/iser: Limit sg tablesize and max_sectors to device fastreg max depth Steve Wise
[not found] ` <20150702151619.12946.79500.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2015-07-05 9:57 ` Sagi Grimberg
[not found] ` <5598FFA3.5020508-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-07-05 13:15 ` Steve Wise [this message]
2015-07-02 15:16 ` [PATCH V4 5/5] RDMA/isert: Limit read depth based on the device max_sge_rd capability Steve Wise
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=55992DD9.2010909@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=infinipath-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=target-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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