From: Avinesh Kumar <avinesh.kumar@suse.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org, wqu@suse.com
Subject: Re: [PATCH] generic/798: exclude nfs from cachestat dirty page reporting test
Date: Wed, 26 Aug 2026 16:39:51 +0200 [thread overview]
Message-ID: <a658f09d-0df6-4c15-bb6b-4e00d0be82cd@suse.com> (raw)
In-Reply-To: <20260824161518.GP839663@frogsfrogsfrogs>
Hello Darrick,
>> diff --git a/tests/generic/798 b/tests/generic/798
>> index 0fe37646..80b2acc9 100755
>> --- a/tests/generic/798
>> +++ b/tests/generic/798
>> @@ -16,6 +16,12 @@ _require_scratch
>> _exclude_scratch_mount_option "dax"
>> _exclude_scratch_mount_option "sync"
>>
>> +# NFS flushes dirty data back to the server on close() as part of its
>> +# close-to-open cache consistency model, so a page written and closed in
>> +# one xfs_io invocation is no longer dirty by the time cachestat runs in
>> +# a later invocation.
>> +_exclude_fs nfs
>
> Could you just chain all the xfs_io commands together into a single
> invocation?
>
> $XFS_IO_PROG -f \
> -c "pwrite -b $pagesize 0 $size" \
> -c "cachestat 0 $size" \
> -c "fsync" \
> -c "cachestat 0 $size" \
> $SCRATCH_MNT/foobar
>
> to solve this problem?
>
Thanks for the review and this suggestion. Chaining all xfs_io commands
together seems to work, with also passing '-q' to pwrite to suppress
these lines -
+wrote 4096/4096 bytes at offset 0
+4 KiB, 1 ops; 0.0000 sec (355.114 MiB/sec and 90909.0909 ops/sec)
I am sending revised patch.
Regards,
Avinesh
next prev parent reply other threads:[~2026-08-26 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 15:11 [PATCH] generic/798: exclude nfs from cachestat dirty page reporting test Avinesh Kumar
2026-08-24 16:15 ` Darrick J. Wong
2026-08-26 14:39 ` Avinesh Kumar [this message]
2026-08-26 15:01 ` [PATCH v2] generic/798: chain xfs_io commands into a single invocation Avinesh Kumar
2026-08-26 15:20 ` Darrick J. Wong
2026-08-26 15:54 ` [PATCH v3] " Avinesh Kumar
2026-08-26 16:15 ` Darrick J. Wong
2026-08-26 17:00 ` Zorro Lang
2026-08-26 22:13 ` Qu Wenruo
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=a658f09d-0df6-4c15-bb6b-4e00d0be82cd@suse.com \
--to=avinesh.kumar@suse.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=wqu@suse.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