From: Christoph Hellwig <hch@lst.de>
To: "Javier González" <javier.gonz@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Dmitry Monakhov <dmtrmonakhov@yandex-team.ru>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
Chaitanya.Kulkarni@wdc.com
Subject: Re: [PATCH 1/1] nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a Samsung PM1725a
Date: Thu, 8 Apr 2021 14:15:38 +0200 [thread overview]
Message-ID: <20210408121538.GA12948@lst.de> (raw)
In-Reply-To: <20210408103016.5girhv5ctkucovmd@mpHalley.local>
On Thu, Apr 08, 2021 at 12:30:16PM +0200, Javier González wrote:
>>> Aligning to MDTS is our current behavior, although all kernels up to
>>> 5.11 had a bug in the calculation.
>>
>> I see. Let me check internally and see what's going on with
>> write-zeroes on this model.
>
> We still need to confirm, but it seems like MDTS for write-zeroes is
> reported wrong in the FW that Dmitry is using. We can at least reproduce
> it.
>
> Would it be a possibility to add quirk infrastructure to hardcode MDTS
> for FW versions prior TP4040?
>
> Another possibility is to add quirks to the TP4040 support patches to
> enable this - it might also help reduce the list of models currently
> blacklisted for write-zeroes.
I'm not sure I understand you. Before TP4040 there is only the MDTS,
which only applies to data transfer commands, although we also
"volunarily" apply it to Write Zeroes. If MDTS is wrong this would
also affect normal I/O, so we really either need a firmware update
or a quirk. Or is the Write Zeroes limit even smaller than MTDS?
I'd rather not add another quirk with a specific limit in that case,
as well grow way too many of those. TP4040 is the way to go for that
case.
next prev parent reply other threads:[~2021-04-08 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1615377076-3251-1-git-send-email-dmtrmonakhov@yandex-team.ru>
2021-03-10 13:21 ` [PATCH 1/1] nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a Samsung PM1725a Christoph Hellwig
2021-03-10 13:41 ` Christoph Hellwig
2021-03-10 20:00 ` Keith Busch
2021-03-11 10:47 ` Christoph Hellwig
2021-03-23 8:37 ` Javier González
2021-03-23 12:31 ` Christoph Hellwig
2021-03-23 12:43 ` Javier González
2021-04-08 10:30 ` Javier González
2021-04-08 12:15 ` Christoph Hellwig [this message]
2021-04-08 18:15 ` Javier González
2021-03-11 10:28 ` Dmitry Monakhov
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=20210408121538.GA12948@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=dmtrmonakhov@yandex-team.ru \
--cc=javier.gonz@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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