From: Nico Pache <npache@redhat.com>
To: fio@vger.kernel.org
Cc: axboe@kernel.dk, vincentfu@gmail.com, npache@redhat.com,
david@kernel.org, willy@infradead.org
Subject: [RFC 0/2] Introduce a page_fault ioengine for MM workflows
Date: Thu, 29 Jan 2026 11:42:59 -0700 [thread overview]
Message-ID: <20260129184302.34887-1-npache@redhat.com> (raw)
This series introduces a new page_fault ioengine and a follow‑up option
to make khugepaged behavior more deterministic for page fault testing.
The first patch adds an mmap‑backed ioengine that allocates anonymous
memory and copies data on read/write to intentionally trigger faults.
This enables using fio’s existing framework and job files for memory
management style workloads without relying on a filesystem. An example
job file is included to demonstrate usage.
The second patch adds a hugepage_delay option to the new engine. It
initially maps memory with MADV_NOHUGEPAGE, then (after a configurable
delay) switches to MADV_HUGEPAGE via a helper thread. This makes
khugepaged candidates reproducible, allows for easier khugepaged testing
and improves repeatability for page_fault tests.
Signed-off-by: Nico Pache <npache@redhat.com>
Nico Pache (2):
page_fault: add mmap-backed ioengine for anonymous faults
page_fault: add hugepage_delay option for delayed MADV_HUGEPAGE
Makefile | 2 +-
cconv.c | 3 +
engines/page_fault.c | 185 ++++++++++++++++++++++++++++++++++++++++
examples/page_fault.fio | 9 ++
options.c | 10 +++
thread_options.h | 3 +
6 files changed, 211 insertions(+), 1 deletion(-)
create mode 100644 engines/page_fault.c
create mode 100644 examples/page_fault.fio
--
2.52.0
next reply other threads:[~2026-01-29 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 18:42 Nico Pache [this message]
2026-01-29 18:43 ` [RFC 1/2] page_fault: add mmap-backed ioengine for anonymous faults Nico Pache
2026-01-29 18:43 ` [RFC 2/2] page_fault: add hugepage_delay option for delayed MADV_HUGEPAGE Nico Pache
2026-01-30 20:08 ` Vincent Fu
2026-02-02 15:24 ` Nico Pache
2026-01-30 21:00 ` [RFC 0/2] Introduce a page_fault ioengine for MM workflows fiotestbot
2026-01-31 13:59 ` Jens Axboe
2026-02-02 15:22 ` Nico Pache
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=20260129184302.34887-1-npache@redhat.com \
--to=npache@redhat.com \
--cc=axboe@kernel.dk \
--cc=david@kernel.org \
--cc=fio@vger.kernel.org \
--cc=vincentfu@gmail.com \
--cc=willy@infradead.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