From: Rita Lin <ritach_lin@phison.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "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: Tue, 27 Sep 2022 07:14:16 +0000 [thread overview]
Message-ID: <3aeb692e9037462b9f9a23a60277b80c@ExMBX2.phison.com> (raw)
In-Reply-To: <20220927070822.GA15262@lst.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 1510 bytes --]
Dear Christoph,
Please find the singed-off-by line below.
//signed-off-by: Tina Hsu <tina_hsu@phison.corp-partner.google.com>//
Reattach the patch again
Thanks
Rita LinÁÖݽìÓ
+886-37-586-896 Ext.80051
ritach_lin@phison.com
-----Original Message-----
From: Christoph Hellwig [mailto:hch@lst.de]
Sent: Tuesday, September 27, 2022 3:08 PM
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-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
On Fri, Sep 23, 2022 at 06:16:01AM +0000, Rita Lin wrote:
> Dear Christoph,
>
> The signed off information was put in line 10 in previous patch.
> I was not able to attach an image to identify the location to you.
I have not been able to find a Signed-off-by: line. Please provide one in reply to this mail.
This message and any attachments are confidential and may be legally privileged. Any unauthorized review, use or distribution by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please immediately notify the sender, completely delete the message and any attachments, and destroy all copies. Your cooperation will be highly appreciated.
[-- Attachment #2: 0001-PATCH-Add-Phison-E3C-E4C-Disable-Write-Zero.patch --]
[-- Type: application/octet-stream, Size: 1421 bytes --]
From 25a32a85ffa26cbbf0649d2b5457f6e13ec85903 Mon Sep 17 00:00:00 2001
From: Tina Hsu <tina_hsu@phison.corp-partner.google.com>
Date: Thu, 22 Sep 2022 14:16:30 +0800
Subject: [PATCH] [PATCH] Add Phison E3C/E4C Disable Write Zero
E3C/E4C 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.
signed-off-by: Tina Hsu <tina_hsu@phison.corp-partner.google.com>
---
drivers/nvme/host/pci.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 98864b853eef..67d3335e9cc8 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -3470,6 +3470,10 @@ static const struct pci_device_id nvme_id_table[] = {
{ PCI_DEVICE(0x1987, 0x5016), /* Phison E16 */
.driver_data = NVME_QUIRK_IGNORE_DEV_SUBNQN |
NVME_QUIRK_BOGUS_NID, },
+ { PCI_DEVICE(0x1987, 0x5019), /* phison E19 */
+ .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x1987, 0x5021), /* Phison E21 */
+ .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x1b4b, 0x1092), /* Lexar 256 GB SSD */
.driver_data = NVME_QUIRK_NO_NS_DESC_LIST |
NVME_QUIRK_IGNORE_DEV_SUBNQN, },
--
2.25.1
next prev parent reply other threads:[~2022-09-27 7:14 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
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 [this message]
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=3aeb692e9037462b9f9a23a60277b80c@ExMBX2.phison.com \
--to=ritach_lin@phison.com \
--cc=Vita.Hsueh@quantatw.com \
--cc=audrey.wang@hp.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=redd_huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox