linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Max Gurtovoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] IB/iser: fix max_sectors calculation
Date: Wed, 27 Apr 2016 18:45:10 +0300	[thread overview]
Message-ID: <5720DE86.6060503@mellanox.com> (raw)
In-Reply-To: <1461013588-8825-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>



On 4/19/2016 12:06 AM, Christoph Hellwig wrote:
> iSER currently has a couple places that set max_sectors in either the host
> template or SCSI host, and all of them get it wrong.
>
> This patch instead uses a single assignment that (hopefully) gets it right:
> the max_sectors value must be derived from the number of segments in the
> FR or FRM structure, but actually be one lower than the page size multiplied

* FRM ==> FMR

> by the number of sectors, as it has to handle the case of non-aligned I/O.
>
> Without this I get trivivial to reproduce hangs when running xfstests
> (on XFS) over iSER to Linux targets.
>
> Signed-off-by: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
> ---
>   drivers/infiniband/ulp/iser/iscsi_iser.c | 14 ++++++++++----
>   1 file changed, 10 insertions(+), 4 deletions(-)
>

Looks good.

Reviewed-by: Max Gurtovoy <maxg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
--
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

  parent reply	other threads:[~2016-04-27 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 21:06 [PATCH] IB/iser: fix max_sectors calculation Christoph Hellwig
     [not found] ` <1461013588-8825-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2016-04-19 14:06   ` Sagi Grimberg
2016-04-27 15:45   ` Max Gurtovoy [this message]
2016-04-28  7:33   ` Or Gerlitz
2016-04-28  7:42   ` Or Gerlitz
     [not found]     ` <CAJ3xEMh1kd_tXVrS73j46ns5syrw2WDTovqVpP0snbLru_fbQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-28  7:55       ` Christoph Hellwig
     [not found]         ` <20160428075508.GA18285-jcswGhMUV9g@public.gmane.org>
2016-04-28 10:51           ` Or Gerlitz
     [not found]             ` <CAJ3xEMj-HX=dRe8zew3VDZ6X_oodzfxX8SwnROCh1T6cfVNTYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-28 16:28               ` Jason Gunthorpe
     [not found]                 ` <20160428162802.GA29690-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-04-28 20:21                   ` Or Gerlitz
     [not found]                     ` <CAJ3xEMjFbtjD4mBHFcd8-msqATgtOpj-fsUh0P-8v1ZZekBXuA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-28 21:11                       ` Jason Gunthorpe
2016-04-28 11:15           ` Sagi Grimberg
     [not found]             ` <5721F0E6.9030806-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2016-04-28 14:02               ` Or Gerlitz
     [not found]                 ` <CAJ3xEMgEm4b5pgcjTD+DyafoZptUiqhp3pYkpKH3eUcNz8iPbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-29 11:06                   ` Sagi Grimberg

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=5720DE86.6060503@mellanox.com \
    --to=maxg-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=hch-jcswGhMUV9g@public.gmane.org \
    --cc=linux-rdma-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;
as well as URLs for NNTP newsgroup(s).