From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>,
qemu-stable@nongnu.org,
Christian Schoenebeck <qemu_oss@crudebyte.com>
Subject: Re: [PATCH v2 0/2] 9pfs: v9fs_reclaim_fd() fixes
Date: Tue, 18 Mar 2025 20:00:19 +0100 [thread overview]
Message-ID: <2853065.71BMcKx459@silver> (raw)
In-Reply-To: <cover.1741339452.git.qemu_oss@crudebyte.com>
On Friday, March 7, 2025 10:24:12 AM CET Christian Schoenebeck wrote:
> Three fixes for 9p server's v9fs_reclaim_fd() function:
>
> * Patch 1 fixes a concurrency issue.
>
> * Patch 2 fixes a file descriptor leak and optimizes overall latency. On a test
> machine with ~800,000 FIDs, this reduced execution duration of
> v9fs_reclaim_fd() from 30ms to 1ms.
>
> V2:
> - Patch 2: Decrement global variable total_open_fd on main thread, not
> on fs driver background thread.
> - Patch 2: Update commit log about file descriptor leak being fixed.
>
> Christian Schoenebeck (2):
> 9pfs: fix concurrent v9fs_reclaim_fd() calls
> 9pfs: fix FD leak and reduce latency of v9fs_reclaim_fd()
>
> hw/9pfs/9p.c | 39 ++++++++++++++++++++++++++++++---------
> hw/9pfs/9p.h | 1 +
> 2 files changed, 31 insertions(+), 9 deletions(-)
>
>
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
/Christian
prev parent reply other threads:[~2025-03-18 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 9:24 [PATCH v2 0/2] 9pfs: v9fs_reclaim_fd() fixes Christian Schoenebeck
2025-03-07 9:22 ` [PATCH v2 1/2] 9pfs: fix concurrent v9fs_reclaim_fd() calls Christian Schoenebeck
2025-03-07 9:23 ` [PATCH v2 2/2] 9pfs: fix FD leak and reduce latency of v9fs_reclaim_fd() Christian Schoenebeck
2025-03-07 9:47 ` Christian Schoenebeck
2025-03-10 9:57 ` Greg Kurz
2025-03-10 9:54 ` Greg Kurz
2025-03-18 19:00 ` Christian Schoenebeck [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=2853065.71BMcKx459@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.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;
as well as URLs for NNTP newsgroup(s).