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, david@kernel.org
Subject: [PATCH v2 2/2] Documentation: update the HOWTO to include the page_fault engine
Date: Wed, 11 Mar 2026 09:51:12 -0600 [thread overview]
Message-ID: <20260311155114.198006-3-npache@redhat.com> (raw)
In-Reply-To: <20260311155114.198006-1-npache@redhat.com>
Document the new page fault engine.
Signed-off-by: Nico Pache <npache@redhat.com>
---
HOWTO.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/HOWTO.rst b/HOWTO.rst
index e712ee2e..421e6408 100644
--- a/HOWTO.rst
+++ b/HOWTO.rst
@@ -2376,6 +2376,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:
--
2.53.0
next prev parent reply other threads:[~2026-03-11 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 15:51 [PATCH v2 0/2] Introduce a page_fault ioengine for MM workflows Nico Pache
2026-03-11 15:51 ` [PATCH v2 1/2] page_fault: add mmap-backed ioengine for anonymous faults Nico Pache
2026-03-12 13:34 ` Vincent Fu
2026-03-12 17:37 ` Nico Pache
2026-03-11 15:51 ` Nico Pache [this message]
2026-03-12 13:35 ` [PATCH v2 2/2] Documentation: update the HOWTO to include the page_fault engine Vincent Fu
2026-03-11 17:08 ` [PATCH v2 0/2] Introduce a page_fault ioengine for MM workflows 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=20260311155114.198006-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