From: Jens Axboe <axboe@kernel.dk>
To: vincentfu@gmail.com, Ankit Kumar <ankit.kumar@samsung.com>
Cc: fio@vger.kernel.org, joshi.k@samsung.com
Subject: Re: [PATCH v2 0/3] Support trim with multiple ranges
Date: Thu, 15 Feb 2024 08:40:36 -0700 [thread overview]
Message-ID: <170801163679.3036043.13144027146541040787.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240215151812.138370-1-ankit.kumar@samsung.com>
On Thu, 15 Feb 2024 20:48:09 +0530, Ankit Kumar wrote:
> NVMe specification allow multiple ranges for the dataset management
> command. The block ioctl only accepts a single entry for trim, but
> with nvme character device we can send multiple ranges.
>
> The first patch in this series adds an option num_range to send multiple
> range per trim request. This will only work if the data direction is
> solely trim i.e. trim or randtrim.
>
> [...]
Applied, thanks!
[1/3] trim: add support for multiple ranges
commit: b3251e31bae2c2ec7c8db0e7e7511eb03b8b0190
[2/3] engines/nvme: pass offset and len instead of io_u
commit: 0d610785a8072eba146dd05f2928a1a89da49bd5
[3/3] engines/io_uring: add multi range dsm support
commit: 5d4ee0de9d6afaa74c7c15c3d4f210a06d4e2139
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-02-15 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240215100103epcas5p3271477465b0155deb7483f26858087ec@epcas5p3.samsung.com>
2024-02-15 15:18 ` [PATCH v2 0/3] Support trim with multiple ranges Ankit Kumar
[not found] ` <CGME20240215100104epcas5p111b3faaa2981ffea3e137adfae2e4a35@epcas5p1.samsung.com>
2024-02-15 15:18 ` [PATCH v2 1/3] trim: add support for " Ankit Kumar
[not found] ` <CGME20240215100105epcas5p412e9121c4520e51a680464f62ee09bb0@epcas5p4.samsung.com>
2024-02-15 15:18 ` [PATCH v2 2/3] engines/nvme: pass offset and len instead of io_u Ankit Kumar
[not found] ` <CGME20240215100106epcas5p2c755350dbd4dd81e04ab0d62bb8c2370@epcas5p2.samsung.com>
2024-02-15 15:18 ` [PATCH v2 3/3] engines/io_uring: add multi range dsm support Ankit Kumar
2024-02-15 15:40 ` Jens Axboe [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=170801163679.3036043.13144027146541040787.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=ankit.kumar@samsung.com \
--cc=fio@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=vincentfu@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).