From: Remi Pommarel <repk@triplefau.lt>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: v9fs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Christian Schoenebeck <linux_oss@crudebyte.com>
Subject: Re: [PATCH v4 0/4] 9p: Performance improvements for build workloads
Date: Mon, 4 May 2026 21:47:17 +0200 [thread overview]
Message-ID: <afj3xZOpaUlvFuIj@pilgrim> (raw)
In-Reply-To: <aeBGIg9aEPFbzZuZ@codewreck.org>
On Thu, Apr 16, 2026 at 11:14:58AM +0900, Dominique Martinet wrote:
> Remi Pommarel wrote on Tue, Mar 24, 2026 at 08:43:30PM +0100:
> > Also sorry for the long delay for v4, it's been quite busy lately.
>
> Thank you for this v4; I've been busy myself so can't complain...
>
> I think we've iterated enough on this for now, so I'll tentatively pick
> this up for -next shortly, but there are a few fixes I'd like to get in
> first and we're a bit late to send this for 7.1, so this cache change
> will be for 7.2 in a couple of months
>
> Meanwhile if there are other comments etc we can always iterate (with
> either a v5 or pilling patches on top)
Thanks but if you can hold that a little bit as sashiko.dev found some
important issues with PATCH 4/4 that must be addressed. A v5 is
comming very shortly with the needed fixes.
Thanks.
--
Remi
prev parent reply other threads:[~2026-05-04 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 19:43 [PATCH v4 0/4] 9p: Performance improvements for build workloads Remi Pommarel
2026-03-24 19:43 ` [PATCH v4 1/4] 9p: Cache negative dentries for lookup performance Remi Pommarel
2026-03-24 19:43 ` [PATCH v4 2/4] 9p: Add mount option for negative dentry cache retention Remi Pommarel
2026-03-24 19:43 ` [PATCH v4 3/4] 9p: Set default negative dentry retention time for cache=loose Remi Pommarel
2026-03-24 19:43 ` [PATCH v4 4/4] 9p: Enable symlink caching in page cache Remi Pommarel
2026-04-16 2:14 ` [PATCH v4 0/4] 9p: Performance improvements for build workloads Dominique Martinet
2026-05-04 19:47 ` Remi Pommarel [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=afj3xZOpaUlvFuIj@pilgrim \
--to=repk@triplefau.lt \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--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