public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Rita Lin <ritach_lin@phison.com>
Cc: "Keith Busch" <kbusch@kernel.org>, "Jens Axboe" <axboe@fb.com>,
	"Christoph Hellwig" <hch@lst.de>,
	"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:31:37 +0200	[thread overview]
Message-ID: <20220922053137.GA27191@lst.de> (raw)
In-Reply-To: <36fd82e8780742c2881f078f98110e5e@ExMBX2.phison.com>

On Thu, Sep 22, 2022 at 02:03:01AM +0000, Rita Lin wrote:
> Dear receivers,
> 
> We would like to apply to disable write zeros support on Phison SSDs.

Can you explain why these SSDs do claim write Zeroes but it doesn't
actually work, and why this is not fixable in a firmware update?

       reply	other threads:[~2022-09-22  5:31 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 ` Christoph Hellwig [this message]
2022-09-22  5:50   ` nvme-pci: disable write zeros support on SSDs 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
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=20220922053137.GA27191@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox