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 2/8] engines: sync: add support for DDIR_SYNCFS
Date: Fri, 27 Feb 2026 14:55:32 +0900	[thread overview]
Message-ID: <20260227055538.2334916-3-dlemoal@kernel.org> (raw)
In-Reply-To: <20260227055538.2334916-1-dlemoal@kernel.org>

Flag the sync IO engine with the FIO_SYNCFS flag to indicate that syncfs
operations are supported. No additional changes are needed to enable
syncfs processing as this IO engine already processes all sync operation
variants using do_io_u_sync().

Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
---
 engines/sync.c | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/engines/sync.c b/engines/sync.c
index 89466ca596aa..ba71ee04801d 100644
--- a/engines/sync.c
+++ b/engines/sync.c
@@ -433,7 +433,7 @@ static struct ioengine_ops ioengine_rw = {
 	.open_file	= generic_open_file,
 	.close_file	= generic_close_file,
 	.get_file_size	= generic_get_file_size,
-	.flags		= FIO_SYNCIO,
+	.flags		= FIO_SYNCIO | FIO_SYNCFS,
 };
 
 static struct ioengine_ops ioengine_prw = {
@@ -443,7 +443,7 @@ static struct ioengine_ops ioengine_prw = {
 	.open_file	= generic_open_file,
 	.close_file	= generic_close_file,
 	.get_file_size	= generic_get_file_size,
-	.flags		= FIO_SYNCIO,
+	.flags		= FIO_SYNCIO | FIO_SYNCFS,
 };
 
 static struct ioengine_ops ioengine_vrw = {
@@ -458,7 +458,7 @@ static struct ioengine_ops ioengine_vrw = {
 	.open_file	= generic_open_file,
 	.close_file	= generic_close_file,
 	.get_file_size	= generic_get_file_size,
-	.flags		= FIO_SYNCIO,
+	.flags		= FIO_SYNCIO | FIO_SYNCFS,
 };
 
 #ifdef CONFIG_PWRITEV
@@ -471,7 +471,7 @@ static struct ioengine_ops ioengine_pvrw = {
 	.open_file	= generic_open_file,
 	.close_file	= generic_close_file,
 	.get_file_size	= generic_get_file_size,
-	.flags		= FIO_SYNCIO,
+	.flags		= FIO_SYNCIO | FIO_SYNCFS,
 };
 #endif
 
@@ -485,8 +485,7 @@ static struct ioengine_ops ioengine_pvrw2 = {
 	.open_file	= generic_open_file,
 	.close_file	= generic_close_file,
 	.get_file_size	= generic_get_file_size,
-	.flags		= FIO_SYNCIO |
-			  FIO_ATOMICWRITES,
+	.flags		= FIO_SYNCIO | FIO_ATOMICWRITES | FIO_SYNCFS,
 	.options	= options,
 	.option_struct_size	= sizeof(struct psyncv2_options),
 };
-- 
2.53.0


  parent 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 [PATCH v3 0/8] Introduce the end_syncfs option Damien Le Moal
2026-02-27  5:55 ` [PATCH v3 1/8] fio: introduce " Damien Le Moal
2026-02-27  5:55 ` Damien Le Moal [this message]
2026-02-27  5:55 ` [PATCH v3 3/8] engines: libaio: add support for DDIR_SYNCFS 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-3-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