All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Christoph Hellwig <hch@lst.de>
Cc: Nicholas Bellinger <nab@linux-iscsi.org>,
	linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: block: remove artifical max_hw_sectors cap
Date: Tue, 30 Dec 2014 15:15:26 +0100	[thread overview]
Message-ID: <54A2B37E.2090104@profihost.ag> (raw)
In-Reply-To: <20141230113206.GA1461@lst.de>


Am 30.12.2014 um 12:32 schrieb Christoph Hellwig:
> On Sun, Dec 28, 2014 at 01:08:59PM +0100, Stefan Priebe wrote:
>>> Nic, can you fix LIO to expose the proper max xfer size?
>>
>> some more problems while running this patch.
>>
>> My crucial m500 and m550 ssds (i have around 60 in 30 different cases and 
>> motherboards but all attached as jbods at LSI HBAs) print those errors:
> 
> What is the max_sectors_kb value for them?
> 
# cat /sys/block/sdi/queue/max_sectors_kb
16383

Greets,
Stefan

  reply	other threads:[~2014-12-30 14:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5497F319.20802@profihost.ag>
2014-12-23  8:28 ` block: remove artifical max_hw_sectors cap Christoph Hellwig
2014-12-28 12:08   ` Stefan Priebe
2014-12-30 11:32     ` Christoph Hellwig
2014-12-30 14:15       ` Stefan Priebe - Profihost AG [this message]
2015-01-05 17:17         ` Christoph Hellwig
2015-01-05 18:40           ` Stefan Priebe
2015-01-06 22:39   ` Nicholas A. Bellinger
2015-01-06 23:41     ` Nicholas A. Bellinger
2015-01-07 14:31     ` Christoph Hellwig
2015-01-07 14:32       ` Stefan Priebe - Profihost AG
2015-01-07 14:37         ` Christoph Hellwig

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=54A2B37E.2090104@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --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.