public inbox for fio@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Vincent Fu <vincentfu@gmail.com>
Subject: [PATCH v3 0/8] Introduce the end_syncfs option
Date: Fri, 27 Feb 2026 14:55:30 +0900	[thread overview]
Message-ID: <20260227055538.2334916-1-dlemoal@kernel.org> (raw)

Jens, Vincent,

This patch series introduces the end_syncfs option and adds support for
it to the main IO engines that can handle regular files.
This new option improves the precision of file system benchmarks when a
large number of files are being handled.

Changes from v2:
 - Reworked patch 1 to build a list of file system mounts per job and
   have the end_syncfs option issue syncfs() call for eacho mounted file
   system when a job write stage completes.
 - Added patch 2 to 7 to support this new option in hte sync, libaio,
   io_uring, fallocate, fileoperations, ftruncate and posixaio IO
   engines.

Damien Le Moal (8):
  fio: introduce the end_syncfs option
  engines: sync: add support for DDIR_SYNCFS
  engines: libaio: add support for DDIR_SYNCFS
  engines: io_uring: add support for DDIR_SYNCFS
  engines: fallocate: add support for DDIR_SYNCFS
  engines: fileoperations: add support for DDIR_SYNCFS
  engines: ftruncate: add support for DDIR_SYNCFS
  engines: posixaio: add support for DDIR_SYNCFS

 HOWTO.rst                |   9 ++-
 backend.c                |  59 ++++++++++++++----
 cconv.c                  |   2 +
 configure                |  21 +++++++
 engines/falloc.c         |   4 +-
 engines/fileoperations.c |   8 +--
 engines/ftruncate.c      |   4 +-
 engines/io_uring.c       |  16 +++--
 engines/libaio.c         |   8 ++-
 engines/posixaio.c       |   8 ++-
 engines/sync.c           |  11 ++--
 file.h                   |  15 +++++
 filesetup.c              | 129 ++++++++++++++++++++++++++++++++++++---
 fio.1                    |   8 ++-
 fio.h                    |   1 +
 helpers.c                |   8 +++
 helpers.h                |   3 +
 init.c                   |   1 +
 io_ddir.h                |   3 +-
 io_u.c                   |   6 +-
 ioengines.c              |  10 ++-
 ioengines.h              |   4 ++
 options.c                |  19 ++++++
 server.h                 |   2 +-
 stat.c                   |   3 +-
 thread_options.h         |   5 +-
 zbd.c                    |   1 +
 27 files changed, 319 insertions(+), 49 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-02-27  6:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  5:55 Damien Le Moal [this message]
2026-02-27  5:55 ` [PATCH v3 1/8] fio: introduce the end_syncfs option Damien Le Moal
2026-02-27  5:55 ` [PATCH v3 2/8] engines: sync: add support for DDIR_SYNCFS Damien Le Moal
2026-02-27  5:55 ` [PATCH v3 3/8] engines: libaio: " Damien Le Moal
2026-02-27  5:55 ` [PATCH v3 4/8] engines: io_uring: " Damien Le Moal
2026-02-27  5:55 ` [PATCH v3 5/8] engines: fallocate: " Damien Le Moal
2026-02-27  5:55 ` [PATCH v3 6/8] engines: fileoperations: " Damien Le Moal
2026-02-27  5:55 ` [PATCH v3 7/8] engines: ftruncate: " Damien Le Moal
2026-02-27  5:55 ` [PATCH v3 8/8] engines: posixaio: " Damien Le Moal
2026-02-27  7:11 ` [PATCH v3 0/8] Introduce the end_syncfs option 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=20260227055538.2334916-1-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --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