public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Damien Le Moal <dlemoal@kernel.org>, io-uring@vger.kernel.org
Subject: [PATCH 2/5] man: fixups for io_uring_prep_cmd_discard.3
Date: Mon, 17 Aug 2026 10:28:29 +0200	[thread overview]
Message-ID: <20260817082837.762276-3-hch@lst.de> (raw)
In-Reply-To: <20260817082837.762276-1-hch@lst.de>

Mention the ioctl this is modelled after instead of the io_uring
cmd used to implement io_uring_prep_cmd_discard.3, and drop an
incorrect plural for page cache.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
---
 man/io_uring_prep_cmd_discard.3 | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/man/io_uring_prep_cmd_discard.3 b/man/io_uring_prep_cmd_discard.3
index 97786726f03b..349df86ff9c9 100644
--- a/man/io_uring_prep_cmd_discard.3
+++ b/man/io_uring_prep_cmd_discard.3
@@ -26,14 +26,14 @@ to start discarding
 at the specified
 .IR offset .
 
-The command is an asynchronous equivalent of
-.B BLOCK_URING_CMD_DISCARD
+The command is an asynchronous equivalent of the
+.B BLKDISCARD
 ioctl with a few differences. It allows multiple parallel discards, and it does
 not exclude concurrent writes and reads. As a result, it may lead to races for
 the data on the disk, if the application has IO inflight for the same ranges
 that the discard operates on. It's the user's responsibility to account for that.
-Furthermore, only best efforts are done to invalidate page caches. The user has
-to make sure that no other inflight requests are modifying or reading the
+Furthermore, only best efforts are done to invalidate the page cache. The user
+has to make sure that no other inflight requests are modifying or reading the
 range(s). If that is the case, it might result in stale page cache and data
 inconsistencies.
 
-- 
2.53.0


  parent reply	other threads:[~2026-08-17  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  8:28 support ZONE_RESET_ALL in liburing v3 Christoph Hellwig
2026-08-17  8:28 ` [PATCH 1/5] configure: shorten the message for the discard command Christoph Hellwig
2026-08-17 18:22   ` Jens Axboe
2026-08-17  8:28 ` Christoph Hellwig [this message]
2026-08-17  8:28 ` [PATCH 3/5] liburing: add io_uring_prep_cmd_zone_reset Christoph Hellwig
2026-08-17  8:28 ` [PATCH 4/5] man: add io_uring_prep_cmd_zone_reset_all.3 man page Christoph Hellwig
2026-08-17  8:28 ` [PATCH 5/5] test: add zone_reset_all command test Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2026-08-12 13:12 support ZONE_RESET_ALL in liburing v2 Christoph Hellwig
2026-08-12 13:12 ` [PATCH 2/5] man: fixups for io_uring_prep_cmd_discard.3 Christoph Hellwig
2026-07-15  6:39 support ZONE_RESET_ALL in liburing Christoph Hellwig
2026-07-15  6:39 ` [PATCH 2/5] man: fixups for io_uring_prep_cmd_discard.3 Christoph Hellwig
2026-07-15  8:28   ` Damien Le Moal

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=20260817082837.762276-3-hch@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=io-uring@vger.kernel.org \
    /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