Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Granados <j.granados@samsung.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: "Kanchan Joshi" <joshi.k@samsung.com>,
	"Jens Axboe" <axboe@kernel.dk>, "Keith Busch" <kbusch@kernel.org>,
	"Christoph Hellwig" <hch@lst.de>,
	linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
	"Javier González" <javier.gonz@samsung.com>,
	"Bart Van Assche" <bvanassche@acm.org>,
	david@fromorbit.com, gost.dev@samsung.com,
	"Hui Qi" <hui81.qi@samsung.com>,
	"Nitesh Shetty" <nj.shetty@samsung.com>
Subject: Re: [PATCH] nvme: enable FDP support
Date: Tue, 14 May 2024 10:44:10 +0200	[thread overview]
Message-ID: <20240514084410.64dk4scblcby2a3o@joelS2.panther.com> (raw)
In-Reply-To: <CB17E82F-C649-4D13-8813-1A6F2D621C51@dubeyko.com>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

On Mon, May 13, 2024 at 10:56:00AM +0300, Viacheslav Dubeyko wrote:
> 
> 
> > On May 10, 2024, at 4:40 PM, Kanchan Joshi <joshi.k@samsung.com> wrote:
> > 
> > Flexible Data Placement (FDP), as ratified in TP 4146a, allows the host
> > to control the placement of logical blocks so as to reduce the SSD WAF.
> > 
> > Userspace can send the data lifetime information using the write hints.
> > The SCSI driver (sd) can already pass this information to the SCSI
> > devices. This patch does the same for NVMe.
> > 
> > Fetches the placement-identifiers (plids) if the device supports FDP.
> > And map the incoming write-hints to plids.
> > 
> 
> 
> Great! Thanks for sharing  the patch.
> 
> Do  we have documentation that explains how, for example, kernel-space
> file system can work with block layer to employ FDP?
> 
> Do  we have FDP support in QEMU already if there is no access to real
> device for testing?
I believe FDP has been in qemu for some time. Look for 73064edfb8
("hw/nvme: flexible data placement emulation  [Jesper Devantier]")

best

-- 

Joel Granados

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2024-05-14  8:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240510134740epcas5p24ef1c2d6e8934c1c79b01c849e7ccb41@epcas5p2.samsung.com>
2024-05-10 13:40 ` [PATCH] nvme: enable FDP support Kanchan Joshi
2024-05-10 19:30   ` Keith Busch
2024-05-11  9:20   ` kernel test robot
2024-05-13  7:56   ` Viacheslav Dubeyko
2024-05-14  8:44     ` Joel Granados [this message]
2024-05-14 18:47     ` Kanchan Joshi
2024-05-14 19:00       ` Viacheslav Dubeyko
2024-05-15  3:30         ` Kanchan Joshi
2024-05-14 21:40           ` Viacheslav Dubeyko
2024-05-17 16:27             ` Kanchan Joshi
2024-05-17 17:22               ` Viacheslav Dubeyko

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=20240514084410.64dk4scblcby2a3o@joelS2.panther.com \
    --to=j.granados@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=david@fromorbit.com \
    --cc=gost.dev@samsung.com \
    --cc=hch@lst.de \
    --cc=hui81.qi@samsung.com \
    --cc=javier.gonz@samsung.com \
    --cc=joshi.k@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nj.shetty@samsung.com \
    --cc=slava@dubeyko.com \
    /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