From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
Avri Altman <avri.altman@wdc.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-scsi@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v2 0/2] Use SYNCHRONIZE CACHE instead of FUA for UFS devices
Date: Thu, 2 Feb 2023 14:00:39 -0800 [thread overview]
Message-ID: <20230202220041.560919-1-bvanassche@acm.org> (raw)
Hi Martin,
Measurements have shown that UFS devices perform better when using SYNCHRONIZE
CACHE instead of FUA. Hence this patch series that makes the SCSI core submit
a SYNCHRONIZE CACHE command instead of setting the FUA bit for UFS
devices. Please consider this patch series for the next merge window.
Thanks,
Bart.
Changes compared to v1:
- Updated __BLIST_LAST_USED.
- Added #include <scsi/scsi_devinfo.h> to fix a build error reported by the
kernel robot.
Asutosh Das (1):
scsi: ufs: Use SYNCHRONIZE CACHE instead of FUA
Bart Van Assche (1):
scsi: core: Introduce the BLIST_BROKEN_FUA flag
drivers/scsi/scsi_scan.c | 3 +++
drivers/ufs/core/ufshcd.c | 4 ++++
include/scsi/scsi_devinfo.h | 4 +++-
3 files changed, 10 insertions(+), 1 deletion(-)
next reply other threads:[~2023-02-02 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 22:00 Bart Van Assche [this message]
2023-02-02 22:00 ` [PATCH v2 1/2] scsi: core: Introduce the BLIST_BROKEN_FUA flag Bart Van Assche
2023-05-05 20:36 ` Bart Van Assche
2023-02-02 22:00 ` [PATCH v2 2/2] scsi: ufs: Use SYNCHRONIZE CACHE instead of FUA Bart Van Assche
2023-02-03 6:30 ` [PATCH v2 0/2] Use SYNCHRONIZE CACHE instead of FUA for UFS devices Christoph Hellwig
2023-02-03 17:54 ` Bart Van Assche
2023-02-08 6:32 ` Christoph Hellwig
2023-02-08 23:55 ` Martin K. Petersen
2023-02-03 15:34 ` Bean Huo
-- strict thread matches above, loose matches on Subject: below --
2023-02-02 21:58 Bart Van Assche
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=20230202220041.560919-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=jaegeuk@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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).