From: Damien Le Moal <dlemoal@kernel.org>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Vincent Fu <vincentfu@gmail.com>
Subject: Re: [PATCH v4 0/8] Introduce the end_syncfs option
Date: Mon, 2 Mar 2026 11:18:59 +0900 [thread overview]
Message-ID: <38e88c6a-7081-4f68-bb57-ffeb2ce5e577@kernel.org> (raw)
In-Reply-To: <CALjAwxj1zbewniV8SNUt9d-qkDGrNAaGPkzp0BtRAdoL71pmUg@mail.gmail.com>
On 3/1/26 7:47 PM, Sitsofe Wheeler wrote:
> On Fri, 27 Feb 2026 at 08:13, Damien Le Moal <dlemoal@kernel.org> wrote:
>>
>> 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.
>
> This looks excellent to me and I especially like that it now groups
> the syncing by the filesystem each file uses. I went through the
> ioengine flags and wondered whether absence of FIO_DISKLESSIO was
> enough to know that an ioengine would support syncfs but there are
> engines (like mmap and sg) that lack FIO_DISKLESSIO but would be
> inappropriate so a new flag makes sense.
>
> Out of idle curiosity, what happens if you use the syncfs option when
> the file being operated on is a device? Regardless:
In add_file_fs(), I have:
if (f->filetype != FIO_TYPE_FILE)
return 0;
So for any file that is not a regular file, we do not try to add a mount
point/FS to the job list and end_syncfs will have no effect for these
non-regular files.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-03-02 2:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 8:07 [PATCH v4 0/8] Introduce the end_syncfs option Damien Le Moal
2026-02-27 8:07 ` [PATCH v4 1/8] fio: introduce " Damien Le Moal
2026-02-27 8:07 ` [PATCH v4 2/8] engines: sync: add support for DDIR_SYNCFS Damien Le Moal
2026-02-27 8:07 ` [PATCH v4 3/8] engines: libaio: " Damien Le Moal
2026-02-27 8:07 ` [PATCH v4 4/8] engines: io_uring: " Damien Le Moal
2026-02-27 8:07 ` [PATCH v4 5/8] engines: fallocate: " Damien Le Moal
2026-02-27 8:07 ` [PATCH v4 6/8] engines: fileoperations: " Damien Le Moal
2026-02-27 8:07 ` [PATCH v4 7/8] engines: ftruncate: " Damien Le Moal
2026-02-27 8:07 ` [PATCH v4 8/8] engines: posixaio: " Damien Le Moal
2026-02-27 9:07 ` [PATCH v4 0/8] Introduce the end_syncfs option fiotestbot
2026-03-01 10:47 ` Sitsofe Wheeler
2026-03-02 2:18 ` Damien Le Moal [this message]
2026-03-02 6:25 ` Jens Axboe
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=38e88c6a-7081-4f68-bb57-ffeb2ce5e577@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sitsofe@gmail.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