From: Christoph Hellwig <hch@lst.de>
To: Rita Lin <ritach_lin@phison.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Keith Busch" <kbusch@kernel.org>, "Jens Axboe" <axboe@fb.com>,
"Sagi Grimberg" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
�S晟�| <redd_huang@phison.com>, "Tina Hsu" <tina_hsu@phison.com>,
"Vita Hsueh (薛伊倩)" <Vita.Hsueh@quantatw.com>,
"Wang, Audrey" <audrey.wang@hp.com>
Subject: Re: nvme-pci: disable write zeros support on SSDs
Date: Thu, 22 Sep 2022 07:52:31 +0200 [thread overview]
Message-ID: <20220922055231.GA27560@lst.de> (raw)
In-Reply-To: <53e4a6192bf746af839d8da90917a248@ExMBX2.phison.com>
On Thu, Sep 22, 2022 at 05:50:52AM +0000, Rita Lin wrote:
> Dear Christoph,
>
> Thank you for your reply.
> These SSDs do support write 0 command and the function was tested without issue.
> But since these SSDs are DRAMless products, the write 0 command will take a lot longer to complete which had impacted the product performance.
> Due to the FW had been frozen, we would like to check if we could apply CL for these 2 products.
please add a comment explaining this to the IDs entry.
next prev parent reply other threads:[~2022-09-22 5:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <36fd82e8780742c2881f078f98110e5e@ExMBX2.phison.com>
2022-09-22 5:31 ` nvme-pci: disable write zeros support on SSDs Christoph Hellwig
2022-09-22 5:50 ` Rita Lin
2022-09-22 5:52 ` Christoph Hellwig [this message]
2022-09-22 6:24 ` Rita Lin
2022-09-22 14:26 ` Christoph Hellwig
2022-09-23 3:18 ` Rita Lin
2022-09-23 6:11 ` Christoph Hellwig
2022-09-23 6:16 ` Rita Lin
2022-09-27 7:08 ` Christoph Hellwig
2022-09-27 7:14 ` Rita Lin
2022-09-27 7:21 ` Christoph Hellwig
2022-10-04 7:20 ` Rita Lin
2022-10-04 7:28 ` Christoph Hellwig
2022-10-04 7:32 ` Rita Lin
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=20220922055231.GA27560@lst.de \
--to=hch@lst.de \
--cc=Vita.Hsueh@quantatw.com \
--cc=audrey.wang@hp.com \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=redd_huang@phison.com \
--cc=ritach_lin@phison.com \
--cc=sagi@grimberg.me \
--cc=tina_hsu@phison.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.