From: Christoph Hellwig <hch@lst.de>
To: "Jim.Lin" <jim.chihjung.lin@gmail.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
jim.lin@siliconmotion.com, cj.chen@siliconmotion.com,
david.yeh@siliconmotion.com, hardaway.tseng@sk.com
Subject: Re: [PATCH] nvme-pci: disable write zeroes for SK Hynix BC901
Date: Tue, 28 Nov 2023 13:57:18 +0100 [thread overview]
Message-ID: <20231128125718.GB7613@lst.de> (raw)
In-Reply-To: <20231128025737.53026-1-jim.lin@siliconmotion.com>
On Tue, Nov 28, 2023 at 10:57:37AM +0800, Jim.Lin wrote:
> SK Hynix BC901 drive write zero will cause Chromebook takes more than 20 mins to switch to developer mode
> "disable write zeroes" can fix this issue and Sk Hynix has been verified.
Did you test this on an upstream kernel with
ommit 1b96f862ecccb3e6f950eba584bebf22955cecc5
Author: Christoph Hellwig <hch@lst.de>
Date: Sun Oct 30 16:50:15 2022 +0100
nvme: implement the DEAC bit for the Write Zeroes command
included? Or in ther words, does this drive not implement DEAC
or does it not work properly? What are the chances of actually
fixing the fimware to work properly? Also WZSL limit does the
drive report?
next prev parent reply other threads:[~2023-11-28 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 2:57 [PATCH] nvme-pci: disable write zeroes for SK Hynix BC901 Jim.Lin
2023-11-28 12:57 ` Christoph Hellwig [this message]
[not found] ` <SEYPR01MB4341EFAA7D4B563BFF903B45FDBCA@SEYPR01MB4341.apcprd01.prod.exchangelabs.com>
[not found] ` <71aae1b4cb0441d0940a5e536f4ffce0@sk.com>
2023-11-29 0:09 ` Keith Busch
2023-12-20 6:04 ` Hardaway (Shih Hung) Tseng SKHYT
2024-01-03 7:36 ` Hardaway (Shih Hung) Tseng SKHYT
2024-01-03 16:10 ` Keith Busch
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=20231128125718.GB7613@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=cj.chen@siliconmotion.com \
--cc=david.yeh@siliconmotion.com \
--cc=hardaway.tseng@sk.com \
--cc=jim.chihjung.lin@gmail.com \
--cc=jim.lin@siliconmotion.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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