From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Kanchan Joshi <joshi.k@samsung.com>,
axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, javier.gonz@samsung.com,
bvanassche@acm.org, gost.dev@samsung.com,
Hui Qi <hui81.qi@samsung.com>,
Nitesh Shetty <nj.shetty@samsung.com>
Subject: Re: [PATCH v2] nvme: enable FDP support
Date: Sat, 8 Jun 2024 07:17:40 +0200 [thread overview]
Message-ID: <20240608051740.GA24010@lst.de> (raw)
In-Reply-To: <ZmMj3d1Rvv-5E6Ey@kbusch-mbp.dhcp.thefacebook.com>
Nacked-by: Christoph Hellwig <hch@lst.de>
This is a really overcomplicated way that does not in any way fit the
FDP use case (which is also rather overcomplicated).
If you want to pass on life time information to a NVMe device please
work with the NVMe technical working group to add the equivalent of
the life time hints added to SCSI as part of the
constrained streams in SBC. It would be implementable in the Linux
nvme driver in a few lines of code, similaly trivially in the device
and actually makes things work.
next prev parent reply other threads:[~2024-06-08 5:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240528151007epcas5p32583675f647553923e5ba4987e9bc6ed@epcas5p3.samsung.com>
2024-05-28 15:02 ` [PATCH v2] nvme: enable FDP support Kanchan Joshi
2024-06-07 15:14 ` Keith Busch
2024-06-08 5:17 ` Christoph Hellwig [this message]
2024-06-10 10:38 ` Kanchan Joshi
2024-06-10 11:27 ` Martin K. Petersen
2024-06-10 11:53 ` Javier González
2024-06-10 11:55 ` [PATCH v2] " Christoph Hellwig
2024-06-10 14:52 ` Keith Busch
2024-06-11 5:47 ` Christoph Hellwig
2024-06-11 14:32 ` Keith Busch
2024-06-11 19:43 ` Martin K. Petersen
2024-06-11 22:42 ` Keith Busch
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=20240608051740.GA24010@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=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