From: Kanchan Joshi <joshi.k@samsung.com>
To: axboe@kernel.dk, kbusch@kernel.org, hch@lst.de, sagi@grimberg.me,
martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com, brauner@kernel.org,
jack@suse.cz, jaegeuk@kernel.org, jlayton@kernel.org,
chuck.lever@oracle.com, bvanassche@acm.org
Cc: linux-nvme@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
gost.dev@samsung.com, vishak.g@samsung.com,
javier.gonz@samsung.com, Kanchan Joshi <joshi.k@samsung.com>
Subject: [PATCH v4 0/5] Write-placement hints and FDP
Date: Mon, 26 Aug 2024 22:36:01 +0530 [thread overview]
Message-ID: <20240826170606.255718-1-joshi.k@samsung.com> (raw)
In-Reply-To: CGME20240826171409epcas5p306ba210a9815e202556778a4c105b440@epcas5p3.samsung.com
Current write-hint infrastructure supports 6 temperature-based data life
hints.
The series extends the infrastructure with a new temperature-agnostic
placement-type hint. New fcntl codes F_{SET/GET}_RW_HINT_EX allow to
send the hint type/value on file. See patch #3 commit description for
the details.
Overall this creates 128 placement hint values [*] that users can pass.
Patch #5 adds the ability to map these new hint values to nvme-specific
placement-identifiers.
Patch #4 restricts SCSI to use only life hint values.
Patch #1 and #2 are simple prep patches.
[*] While the user-interface can support more, this limit is due to the
in-kernel plumbing consideration of the inode size. Pahole showed 32-bit
hole in the inode, but the code had this comment too:
/* 32-bit hole reserved for expanding i_fsnotify_mask */
Not must, but it will be good to know if a byte (or two) can be used
here.
Changes since v3:
- 4 new patches to introduce write-placement hints
- Make nvme patch use the placement hints rather than write-life hints
Changes since v2:
- Base it on nvme-6.11 and resolve a merge conflict
Changes since v1:
- Reduce the fetched plids from 128 to 6 (Keith)
- Use struct_size for a calculation (Keith)
- Handle robot/sparse warning
Kanchan Joshi (4):
fs, block: refactor enum rw_hint
fcntl: rename rw_hint_* to rw_life_hint_*
fcntl: add F_{SET/GET}_RW_HINT_EX
nvme: enable FDP support
Nitesh Shetty (1):
sd: limit to use write life hints
drivers/nvme/host/core.c | 81 ++++++++++++++++++++++++++++++++++++++
drivers/nvme/host/nvme.h | 4 ++
drivers/scsi/sd.c | 7 ++--
fs/buffer.c | 4 +-
fs/f2fs/f2fs.h | 4 +-
fs/f2fs/segment.c | 4 +-
fs/fcntl.c | 79 ++++++++++++++++++++++++++++++++++---
include/linux/blk-mq.h | 2 +-
include/linux/blk_types.h | 2 +-
include/linux/fs.h | 2 +-
include/linux/nvme.h | 19 +++++++++
include/linux/rw_hint.h | 20 +++++++---
include/uapi/linux/fcntl.h | 14 +++++++
13 files changed, 218 insertions(+), 24 deletions(-)
--
2.25.1
next parent reply other threads:[~2024-08-26 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240826171409epcas5p306ba210a9815e202556778a4c105b440@epcas5p3.samsung.com>
2024-08-26 17:06 ` Kanchan Joshi [this message]
2024-08-26 17:06 ` [PATCH v4 1/5] fs, block: refactor enum rw_hint Kanchan Joshi
2024-08-26 17:44 ` Bart Van Assche
2024-08-27 5:12 ` Kanchan Joshi
2024-08-30 12:17 ` Bart Van Assche
2024-09-02 5:18 ` Kanchan Joshi
2024-08-26 17:06 ` [PATCH v4 2/5] fcntl: rename rw_hint_* to rw_life_hint_* Kanchan Joshi
2024-08-26 17:06 ` [PATCH v4 3/5] fcntl: add F_{SET/GET}_RW_HINT_EX Kanchan Joshi
2024-08-26 17:06 ` [PATCH v4 4/5] sd: limit to use write life hints Kanchan Joshi
2024-08-26 17:06 ` [PATCH v4 5/5] nvme: enable FDP support Kanchan Joshi
2024-09-06 16:04 ` Keith Busch
2024-09-10 9:25 ` Kanchan Joshi
2024-08-30 11:59 ` [PATCH v4 0/5] Write-placement hints and FDP Javier González
2024-09-03 14:28 ` Kanchan Joshi
2024-09-03 14:35 ` Christian Brauner
2024-09-04 14:57 ` Kanchan Joshi
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=20240826170606.255718-1-joshi.k@samsung.com \
--to=joshi.k@samsung.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=bvanassche@acm.org \
--cc=chuck.lever@oracle.com \
--cc=gost.dev@samsung.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=javier.gonz@samsung.com \
--cc=jlayton@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sagi@grimberg.me \
--cc=vishak.g@samsung.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