From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Randall Huang <ihhuang@abmail.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
jejb@linux.vnet.ibm.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, huangrandall@google.com
Subject: Re: [PATCH] scsi: associate bio write hint with WRITE CDB
Date: Fri, 04 Jan 2019 01:11:49 -0500 [thread overview]
Message-ID: <yq15zv56jfe.fsf@oracle.com> (raw)
In-Reply-To: <20190104052251.GA205256@google.com> (Randall Huang's message of "Fri, 4 Jan 2019 13:22:51 +0800")
Hi Randall,
> I am working on Android phone.
> The idea is to enable write hint for Turbo write UFS feature. Turbo
> write feature in UFS 3.x is under discussion in JEDEC JC-64. This
> patch is the under-lying framework for supporting this feature.
OK, but we can't blindly go setting GROUP NUMBER to a non-zero value.
That'll break a massive amount of devices which will fail READ/WRITE
commands with INVALID FIELD IN CDB.
So aside from requiring the device to report GROUP_SUP=1, we'll need
some sort of indication that this device supports the UFS Turbo Write
feature. If you are engaged with JEDEC on this, please tell them we'll
need a VPD page, a mode page, or something similar to use as trigger to
entertain enabling this feature.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-01-04 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181226041504.66283-1-huangrandall@google.com>
[not found] ` <20190103075133.GA5141@infradead.org>
2019-01-03 9:47 ` [PATCH] scsi: associate bio write hint with WRITE CDB Randall Huang
2019-01-03 21:00 ` Douglas Gilbert
2019-01-03 21:40 ` Ewan D. Milne
2019-01-04 4:57 ` Martin K. Petersen
2019-01-04 5:22 ` Randall Huang
2019-01-04 6:11 ` Martin K. Petersen [this message]
2019-01-10 17:33 ` Alex Lemberg
2019-01-03 9:55 Randall Huang
-- strict thread matches above, loose matches on Subject: below --
2019-01-03 9:19 Randall Huang
2018-12-26 5:51 Randall Huang
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=yq15zv56jfe.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=huangrandall@google.com \
--cc=ihhuang@abmail.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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).