From: Christoph Hellwig <hch@lst.de>
To: Kanchan Joshi <joshi.k@samsung.com>
Cc: Christoph Hellwig <hch@lst.de>,
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 17:08:46 +0200 [thread overview]
Message-ID: <20240703150846.GA1028@lst.de> (raw)
In-Reply-To: <f79cc36c-cd03-bb5e-2eae-3612176a474e@samsung.com>
On Wed, Jul 03, 2024 at 02:10:24PM +0530, Kanchan Joshi wrote:
> That was not the design goal of FDP. It is ludicrous for any storage
> technology to have that as an intentional design choice.
I think you missed out on the development dramas. The Meta
representative for what became FDP absoutely rejected any proposal to
make it useful just for that reason, and anyone outside a small
circle got explicitly excluded from the development for just this
reasons. This is probably as much as I can say without getting in
trouble here, but I'm happy to provide more details in private.
> 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.
Then let's design something proper. It's not that hard. No one
needs to support anything, and between all the major design issues
in FDP and all the political crap thrown by Meta and Samsuns at the
interests of Linux there's no way I can support this.
prev parent reply other threads:[~2024-07-03 15:08 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
2024-07-03 15:08 ` Christoph Hellwig [this message]
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=20240703150846.GA1028@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=gost.dev@samsung.com \
--cc=hui81.qi@samsung.com \
--cc=javier.gonz@samsung.com \
--cc=joshi.k@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