linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: mchristi@redhat.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi: add Synology to 1024 sector blacklist
Date: Wed, 13 Jan 2016 10:41:20 +0100	[thread overview]
Message-ID: <56961BC0.6090101@redhat.com> (raw)
In-Reply-To: <1452677624.27508.70.camel@haakon3.risingtidesystems.com>



On 13/01/2016 10:33, Nicholas A. Bellinger wrote:
>>> This results in IO errors when
>>> handling large IOs. This patch just has us use the old 1024 default
>>> sectors for this target by adding it to the scsi blacklist. We do
>>> not have good contacs with this vendors, so I have not been able to
>>> try and fix on their side.
>>
>> IIRC I saw similar problems a
>> couple years ago with LIO because iscsit_map_iovec maps everything a
>> page at a time and produced too large an iovec for the underlying
>> storage.  I'm afraid you're going to get this for pretty much every user
>> of LIO.
> 
> Two points here.
> 
> We've been exposing backend dev->dev_attrib.hw_max_sectors settings for
> block limits EVPD for FILEIO based on iov limits, and IBLOCK based on
> queue_max_hw_sectors() for some time now.
> 
> So initiators that honor block limits EVPD will work as expected.

What I was describing is more like the backend request_queue's
queue_max_segments influencing the backend's hw_max_sectors.  Is that
covered as well?

Paolo

  reply	other threads:[~2016-01-13  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 22:34 [PATCH 1/1] scsi: add Synology to 1024 sector blacklist mchristi
2016-01-08  2:44 ` Martin K. Petersen
2016-01-12 17:54 ` Paolo Bonzini
2016-01-13  9:33   ` Nicholas A. Bellinger
2016-01-13  9:41     ` Paolo Bonzini [this message]
2016-01-13  9:56       ` Nicholas A. Bellinger
2016-01-13 10:27         ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2015-05-22 19:22 michaelc

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=56961BC0.6090101@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mchristi@redhat.com \
    --cc=nab@linux-iscsi.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).