From: Kanchan Joshi <joshi.k@samsung.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, kbusch@kernel.org, martin.petersen@oracle.com,
sagi@grimberg.me, linux-nvme@lists.infradead.org,
bvanassche@acm.org, javier.gonz@samsung.com,
gost.dev@samsung.com, Hui Qi <hui81.qi@samsung.com>,
Nitesh Shetty <nj.shetty@samsung.com>
Subject: Re: [PATCH v3] nvme: enable FDP support
Date: Wed, 3 Jul 2024 14:10:24 +0530 [thread overview]
Message-ID: <f79cc36c-cd03-bb5e-2eae-3612176a474e@samsung.com> (raw)
In-Reply-To: <20240702113954.GA15325@lst.de>
On 7/2/2024 5:09 PM, Christoph Hellwig wrote:
> Same NAK as before. FDP was intentionally designed to not fit the
> clearly documented Linux needs.
That was not the design goal of FDP. It is ludicrous for any storage
technology to have that as an intentional design choice.
> If you want support for Linux data
> temperature hints work with the NVMe technical working group to make
> it happen.
The value does not come from the temperature-sensitive names that we
have in Linux. It rather comes from keeping the WAF low and from using
Linux file-sytems. The write-hint interface, despite not being ideal,
happens to be the only interface we got for the latter.
If/when anything different grows in the device-side, we can trivially
change the plumbing this patch does.
People need support for what we have in current spec and more
importantly in products. It's not a Meta/Samsung only thing. Many
hypsercalers and enterprise customers need this.
next prev parent reply other threads:[~2024-07-03 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240702103348epcas5p1015eafbddf4795558843cd74b0453b12@epcas5p1.samsung.com>
2024-07-02 10:26 ` [PATCH v3] nvme: enable FDP support Kanchan Joshi
2024-07-02 11:39 ` Christoph Hellwig
2024-07-02 15:15 ` Keith Busch
2024-07-02 15:36 ` Christoph Hellwig
2024-07-02 15:49 ` Jens Axboe
2024-07-02 15:51 ` Christoph Hellwig
2024-07-03 8:40 ` Kanchan Joshi [this message]
2024-07-03 15:08 ` Christoph Hellwig
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=f79cc36c-cd03-bb5e-2eae-3612176a474e@samsung.com \
--to=joshi.k@samsung.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gost.dev@samsung.com \
--cc=hch@lst.de \
--cc=hui81.qi@samsung.com \
--cc=javier.gonz@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=nj.shetty@samsung.com \
--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