From: Christoph Hellwig <hch@lst.de>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Christoph Hellwig <hch@lst.de>,
"Nicholas A. 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: Wed, 7 Jan 2015 15:37:05 +0100 [thread overview]
Message-ID: <20150107143705.GA888@lst.de> (raw)
In-Reply-To: <54AD4389.6030107@profihost.ag>
On Wed, Jan 07, 2015 at 03:32:41PM +0100, Stefan Priebe - Profihost AG wrote:
> > If I understand Stefan correct he was using a recent 3.19-rc kernel,
> > which contains my commit in the subject that stops capping the
> > max_sectors used by the kernel below that which the hardware supports.
> >
> > Given that LIO actually implements the block limits EVPD that suggests
> > we're not properly using that information.
> >
> > Stefant, what does:
> >
> > sg_vpd -p bl /dev/sdX
> >
> > for the LIO device tell?
>
> I'm sorry i'm using a 3.10.63 vanilla kernel. So i'm missing a commit?
You said "block: remove artifical max_hw_sectors cap" causes the I/O
errors for you, which should only be in a 3.19-ish kernel.
prev parent reply other threads:[~2015-01-07 14:37 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
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 [this message]
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=20150107143705.GA888@lst.de \
--to=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=s.priebe@profihost.ag \
--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.