From: Dominique Martinet <asmadeus@codewreck.org>
To: Christian Schoenebeck <linux_oss@crudebyte.com>
Cc: Pierre Barre <pierre@barre.sh>,
ericvh@kernel.org, lucho@ionkov.net,
David Howells <dhowells@redhat.com>,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] 9p: fix i_size update race in getattr with writeback caching
Date: Sun, 15 Feb 2026 18:21:42 +0900 [thread overview]
Message-ID: <aZGQJsgPxuLqlJ_-@codewreck.org> (raw)
In-Reply-To: <1946294.tdWV9SEqCh@weasel>
Christian Schoenebeck wrote on Wed, Feb 04, 2026 at 12:48:55PM +0100:
> > FWIW, I tested the initial approach I described and this seems to result in
> > no real performance improvements compared to not using any writeback
> > caching at all.
>
> Right, surprisingly I don't measure a performance penalty either.
>
> Dominique, suggestions how to proceed on this issue?
Thanks for the ping and sorry for lack of activity lately.
I've just pinged David on IRC (and will remind him monday if no news) as
I don't have enough opinion here..
I'd be tempted to agree with your initial review that this v2 should be
enough though, so unless he has any reason to disagree I'll pick it up
and send to Linus after rc1
--
Dominique Martinet | Asmadeus
next prev parent reply other threads:[~2026-02-15 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 18:01 [PATCH v2] 9p: fix i_size update race in getattr with writeback caching Pierre Barre
2026-01-05 11:35 ` Christian Schoenebeck
2026-01-07 0:27 ` Pierre Barre
2026-02-04 11:48 ` Christian Schoenebeck
2026-02-15 9:21 ` Dominique Martinet [this message]
2026-02-17 14:48 ` David Howells
2026-02-17 15:05 ` David Howells
2026-02-17 16:54 ` David Howells
2026-02-18 13:38 ` David Howells
2026-02-18 13:41 ` David Howells
2026-02-18 14:11 ` Dominique Martinet
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=aZGQJsgPxuLqlJ_-@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=dhowells@redhat.com \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=pierre@barre.sh \
--cc=v9fs@lists.linux.dev \
/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