All of lore.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, npache@redhat.com,
	david@kernel.org
Subject: [PATCH v3 0/2] page_fault: add mmap-backed ioengine for anonymous faults
Date: Tue,  7 Apr 2026 19:20:01 -0600	[thread overview]
Message-ID: <20260408012004.198115-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 and lays the groundwork
for how we plan on utilizing fio to test a number of MM related workloads.

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.

V3:
- Correctly use clang-format to adhere to formatting conventions
- check (and fail/warn) if user sets the start_offset
- directly utilize io_ops_data as there is no files
- updated error/print to follow proper format
- Copy docs update to fio.1

V2: https://lore.kernel.org/fio/20260311155114.198006-1-npache@redhat.com/
V1: https://lore.kernel.org/fio/20260129184302.34887-1-npache@redhat.com/

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

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

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

-- 
2.53.0


             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 Nico Pache [this message]
2026-04-08  1:20 ` [PATCH v3 1/2] page_fault: add mmap-backed ioengine for anonymous faults Nico Pache
2026-04-08  1:20 ` [PATCH v3 2/2] Documentation: update the documentation to include the page_fault engine Nico Pache
2026-04-08  2:01 ` [PATCH v3 0/2] page_fault: add mmap-backed ioengine for anonymous faults 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-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.