From: Dominique Martinet <asmadeus@codewreck.org>
To: Remi Pommarel <repk@triplefau.lt>
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: Thu, 16 Apr 2026 11:14:58 +0900 [thread overview]
Message-ID: <aeBGIg9aEPFbzZuZ@codewreck.org> (raw)
In-Reply-To: <cover.1774380535.git.repk@triplefau.lt>
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,
--
Dominique
next prev parent reply other threads:[~2026-04-16 2:15 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 ` Dominique Martinet [this message]
2026-05-04 19:47 ` [PATCH v4 0/4] 9p: Performance improvements for build workloads Remi Pommarel
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=aeBGIg9aEPFbzZuZ@codewreck.org \
--to=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=repk@triplefau.lt \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.