From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Kanchan Joshi <joshi.k@samsung.com>,
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: Tue, 2 Jul 2024 17:51:20 +0200 [thread overview]
Message-ID: <20240702155120.GC1037@lst.de> (raw)
In-Reply-To: <d7a308f4-7b1f-4136-b655-c72474992151@kernel.dk>
On Tue, Jul 02, 2024 at 09:49:35AM -0600, Jens Axboe wrote:
> I'm with Keith on this one - there's no real maintenance burden to bear
> for this feature, it's pretty well contained. There's no point gate
> keeping it based on changing the spec, as that will take a long time to
> get done. And there's no reason to hold this back until this happens
> based on mostly ideological reasons, when there are actual users that
> could use it now. What do we have to lose?
What we do is a misuse of the spec intentionally designed to not
accomodate us. I'm dead-set against this. Please all help getting
the proper interface in. I worked with folks on the SCSI side and
we finally got it (although with a few warts).
>
next prev parent reply other threads:[~2024-07-02 15:51 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 [this message]
2024-07-03 8:40 ` Kanchan Joshi
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=20240702155120.GC1037@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.