From: Dave Chinner <david@fromorbit.com>
To: Mitta Sai Chaithanya <mittas@microsoft.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Nilesh Awate <Nilesh.Awate@microsoft.com>,
Ganesan Kalyanasundaram <ganesanka@microsoft.com>,
Pawan Sharma <sharmapawan@microsoft.com>
Subject: Re: [EXTERNAL] Re: XFS: Approach to persist data & metadata changes on original file before IO acknowledgment when file is reflinked
Date: Tue, 10 Dec 2024 09:23:37 +1100 [thread overview]
Message-ID: <Z1dt6RmCyMtIlCPW@dread.disaster.area> (raw)
In-Reply-To: <PUZP153MB07284BD46AB65F734B0FBB76D7312@PUZP153MB0728.APCP153.PROD.OUTLOOK.COM>
On Fri, Dec 06, 2024 at 12:43:03PM +0000, Mitta Sai Chaithanya
wrote:
> Thanks Dave Chinner for taking time and explaining in detail, we
> are exposing XFS files through SPDK mechanism and as you pointed
I have no idea what a "SPDK mechanism" is - there isn't a single hit
in the kernel tree on "SPDK"....
> for having low latencies we are writing to the file asynchronously
> (using uring as default configuration). I have one follow up
> question "Will be there any journal updates for future IOs when
> entire file is explicitly zeroe'd and synced for future IOs"?
Yes: mtime updates.
These are asynchronous transactions, though, and if you are using
O_DSYNC/RWF_DSYNC will not directly trigger journal flushes. If you
use fsync/O_SYNC/RWF_SYNC, then mtime update will trigger journal
flushes.
You can use the lazytime mount option to avoid transactional mtime
updates if necessary (only syncs mtime updates from write() calls
when the file is otherwise modified or evicted from cache).
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2024-12-09 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 10:41 XFS: Approach to persist data & metadata changes on original file before IO acknowledgment when file is reflinked Mitta Sai Chaithanya
2024-12-02 23:40 ` Dave Chinner
2024-12-06 12:43 ` [EXTERNAL] " Mitta Sai Chaithanya
2024-12-09 22:23 ` Dave Chinner [this message]
2024-12-10 4:43 ` Christoph Hellwig
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=Z1dt6RmCyMtIlCPW@dread.disaster.area \
--to=david@fromorbit.com \
--cc=Nilesh.Awate@microsoft.com \
--cc=ganesanka@microsoft.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mittas@microsoft.com \
--cc=sharmapawan@microsoft.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