From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-fsdevel@vger.kernel.org, linux-man@vger.kernel.org
Subject: RWF_DONTCACHE documentation
Date: Mon, 2 Jun 2025 08:00:50 -0700 [thread overview]
Message-ID: <aD28onWyzS-HgNcB@infradead.org> (raw)
Hi Jens,
I just tried to reference RWF_DONTCACHE semantics in a standards
discussion, but it doesn't seem to be documented in the man pages
or in fact anywhere else I could easily find. Could you please write
up the semantics for the preadv2/pwritev2 man page?
next reply other threads:[~2025-06-02 15:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 15:00 Christoph Hellwig [this message]
2025-06-02 15:49 ` RWF_DONTCACHE documentation Jens Axboe
2025-06-02 20:54 ` Jens Axboe
2025-06-11 8:41 ` Alejandro Colomar
2025-08-11 17:25 ` Jens Axboe
2025-08-18 4:01 ` Alejandro Colomar
2025-08-18 20:42 ` Jens Axboe
2025-09-01 14:22 ` [PATCH v2] man/man2/readv.2: Document RWF_DONTCACHE Alejandro Colomar
2025-09-01 14:34 ` Alejandro Colomar
2025-09-01 14:36 ` Jens Axboe
2025-09-02 5:21 ` Christoph Hellwig
2025-06-03 6:20 ` RWF_DONTCACHE documentation Johannes Thumshirn
2025-06-03 13:10 ` Jens Axboe
2025-06-03 18:19 ` Johannes Thumshirn
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=aD28onWyzS-HgNcB@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@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;
as well as URLs for NNTP newsgroup(s).