From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: tom.ty89@gmail.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] sd: do not let LBPME bit stop the VPDs speak
Date: Wed, 09 Mar 2016 21:24:29 -0500 [thread overview]
Message-ID: <yq1mvq7qdcy.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <56df97e0.d08d420a.58e8f.3162@mx.google.com> (tom's message of "Wed, 9 Mar 2016 11:26:16 +0800")
>>>>> "Tom" == tom ty89 <tom.ty89@gmail.com> writes:
Tom,
Tom> Some devices have details of their support on unmapping on the
Tom> Block Limits and/or Logical Block Provisioning VPDs while they do
Tom> not set the LBPME bit to 1. Though this is required by the SCSI
Tom> standards, the VPDs are giving even more concrete details about the
Tom> support, so they should be used even when the bit is set to 0.
I am not going to enable an already brittle feature if a device can't
report the right thing.
Does the bridge report LBPME=1 if you plug in an SSD?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-03-10 2:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 3:26 [PATCH 1/1] sd: do not let LBPME bit stop the VPDs speak tom.ty89
2016-03-09 3:30 ` Tom Yan
2016-03-09 3:38 ` Tom Yan
2016-03-10 2:32 ` Martin K. Petersen
[not found] ` <CAGnHSEng46jz66wkhiA73vvgfFzNx+3R4WeBLbyBrhD5UR6NBw@mail.gmail.com>
2016-03-10 8:15 ` Fwd: " Tom Yan
2016-03-11 2:08 ` Martin K. Petersen
2016-03-10 2:24 ` Martin K. Petersen [this message]
[not found] ` <CAGnHSEnHG5i3EvwmcGZU5BXobUCQa7P+j+KKNrUyoS86s7d8Gg@mail.gmail.com>
2016-03-10 8:15 ` Tom Yan
2016-03-11 2:02 ` Martin K. Petersen
2016-03-10 10:33 ` Tom Yan
[not found] ` <CAGnHSEkLo7sp5PUqzk74aZi6r30hVDaj2fD-i_cCHWdezZNPwA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-11 3:26 ` Tom Yan
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=yq1mvq7qdcy.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tom.ty89@gmail.com \
/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.