From: Nico Pache <npache@redhat.com>
To: vincentfu@gmail.com, axboe@kernel.dk, fio@vger.kernel.org
Cc: jvozar@redhat.com, jjurca@redhat.com, jhladky@redhat.com,
peterx@redhat.com, spetrovi@redhat.com, npache@redhat.com,
david@kernel.org
Subject: [PATCH v3 2/2] Documentation: update the documentation to include the page_fault engine
Date: Tue, 7 Apr 2026 19:20:03 -0600 [thread overview]
Message-ID: <20260408012004.198115-3-npache@redhat.com> (raw)
In-Reply-To: <20260408012004.198115-1-npache@redhat.com>
Document the new page fault engine.
Signed-off-by: Nico Pache <npache@redhat.com>
---
HOWTO.rst | 5 +++++
fio.1 | 5 +++++
2 files changed, 10 insertions(+)
diff --git a/HOWTO.rst b/HOWTO.rst
index 5e3266df..bb97ee22 100644
--- a/HOWTO.rst
+++ b/HOWTO.rst
@@ -2379,6 +2379,11 @@ I/O engine
several instances to access the same device or file
simultaneously, but allow it for threads.
+ **page_fault**
+ I/O engine that uses an mmap region to simulate data transfer by
+ allocating anonymous memory and copying data on read/write to
+ intentionally trigger page faults.
+
File/directory operation engines define how the job operates file or directory. The
following types are defined:
diff --git a/fio.1 b/fio.1
index 664d7e3b..14ea6427 100644
--- a/fio.1
+++ b/fio.1
@@ -2168,6 +2168,11 @@ instance is used per process, so all jobs setting option \fBthread\fR will share
a single instance (with one queue per thread) and must specify compatible
options. Note that some drivers don't allow several instances to access the same
device or file simultaneously, but allow it for threads.
+.TP
+.B page_fault
+I/O engine that uses an mmap region to simulate data transfer by allocating
+anonymous memory and copying data on read/write to intentionally trigger page
+faults.
.RE
.P
File/directory operation engines define how the job operates file or directory.
--
2.53.0
next prev parent reply other threads:[~2026-04-08 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 1:20 [PATCH v3 0/2] page_fault: add mmap-backed ioengine for anonymous faults Nico Pache
2026-04-08 1:20 ` [PATCH v3 1/2] " Nico Pache
2026-04-08 1:20 ` Nico Pache [this message]
2026-04-08 2:01 ` [PATCH v3 0/2] " Jens Axboe
2026-04-08 13:21 ` Nico Pache
2026-04-08 4:12 ` fiotestbot
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=20260408012004.198115-3-npache@redhat.com \
--to=npache@redhat.com \
--cc=axboe@kernel.dk \
--cc=david@kernel.org \
--cc=fio@vger.kernel.org \
--cc=jhladky@redhat.com \
--cc=jjurca@redhat.com \
--cc=jvozar@redhat.com \
--cc=peterx@redhat.com \
--cc=spetrovi@redhat.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