From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Async client v4 mount results in unexpected number of extents on the server
Date: Sat, 12 Apr 2025 21:19:03 +0200 [thread overview]
Message-ID: <f2bc2b85-97ee-e00b-bcfd-14a93349bdee@applied-asynchrony.com> (raw)
In-Reply-To: <85AA0B5B-64BF-4308-8730-D62AF68F23A2@redhat.com>
On 2025-04-12 19:28, Benjamin Coddington wrote:
> There isn't any guarantee of write processing order for async writes, is
> there? I also don't think there's any practical impact. So I'm wondering
> what's the expectation of behavior and what problem you're trying to fix?
This definitely does not happen with regular local page writeback.
As I said before, my expectation that NFS behaves the same way might be
overly pedantic, but then again I'm still curious why this happens and whether
it's a bug or just accidental behaviour. *shrug*
Anway thanks for taking a look.
Holger
prev parent reply other threads:[~2025-04-12 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 12:55 Async client v4 mount results in unexpected number of extents on the server Holger Hoffstätte
2025-04-11 13:29 ` Benjamin Coddington
2025-04-12 12:36 ` Holger Hoffstätte
2025-04-12 17:28 ` Benjamin Coddington
2025-04-12 19:19 ` Holger Hoffstätte [this message]
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=f2bc2b85-97ee-e00b-bcfd-14a93349bdee@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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