public inbox for fio@vger.kernel.org
 help / color / mirror / Atom feed
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 0/2] Introduce a page_fault ioengine for MM workflows
Date: Wed, 11 Mar 2026 09:51:10 -0600	[thread overview]
Message-ID: <20260311155114.198006-1-npache@redhat.com> (raw)

This series introduces a new page_fault ioengine for Anonymous memory
testing. 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 first patch adds the mmap‑backed ioengine that allocates anonymous
memory and copies data on read/write to intentionally trigger faults.

The second patch updates the documentation to guide usage of the new
feature.

V2:
- drop the khugepaged_delay, and all other additional features. This
  provides a clean initial implmentation. Further features will be added
  in future series as we keep testing and discover what will be useful
  for functional and performance testing.
- Changed the byte-by-byte r/w to leverage memcpy
- provide a number of test cases
- hardened the engine by limiting what parameters it can accept,
  preventing undefined or broken behavior
- Use clang-format to adhere to formatting conventions

Signed-off-by: Nico Pache <npache@redhat.com>

Nico Pache (2):
  page_fault: add mmap-backed ioengine for anonymous faults
  Documentation: update the HOWTO to include the page_fault engine

 HOWTO.rst               |   5 ++
 Makefile                |   2 +-
 engines/page_fault.c    | 116 ++++++++++++++++++++++++++++++++++++++++
 examples/page_fault.fio |  60 +++++++++++++++++++++
 4 files changed, 182 insertions(+), 1 deletion(-)
 create mode 100644 engines/page_fault.c
 create mode 100644 examples/page_fault.fio

-- 
2.53.0


             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 Nico Pache [this message]
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 ` [PATCH v2 2/2] Documentation: update the HOWTO to include the page_fault engine Nico Pache
2026-03-12 13:35   ` 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-1-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