From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>, qemu-stable@nongnu.org
Subject: [PATCH 0/2] 9pfs: v9fs_reclaim_fd() fixes
Date: Tue, 4 Mar 2025 16:17:48 +0100 [thread overview]
Message-ID: <cover.1741101468.git.qemu_oss@crudebyte.com> (raw)
Two fixes for 9p server's v9fs_reclaim_fd() function:
* Patch 1 fixes a concurrency issue.
* Patch 2 optimizes overall latency. On a test machine with ~800,000 FIDs, this
reduced execution duration of v9fs_reclaim_fd() from 30ms to 1ms.
Christian Schoenebeck (2):
9pfs: fix concurrent v9fs_reclaim_fd() calls
9pfs: reduce latency of v9fs_reclaim_fd()
hw/9pfs/9p.c | 36 +++++++++++++++++++++++++++---------
hw/9pfs/9p.h | 1 +
2 files changed, 28 insertions(+), 9 deletions(-)
--
2.39.5
next reply other threads:[~2025-03-04 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 15:17 Christian Schoenebeck [this message]
2025-03-04 15:15 ` [PATCH 1/2] 9pfs: fix concurrent v9fs_reclaim_fd() calls Christian Schoenebeck
2025-03-06 7:38 ` Greg Kurz
2025-03-04 15:16 ` [PATCH 2/2] 9pfs: reduce latency of v9fs_reclaim_fd() Christian Schoenebeck
2025-03-06 9:07 ` Greg Kurz
2025-03-06 15:11 ` Christian Schoenebeck
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=cover.1741101468.git.qemu_oss@crudebyte.com \
--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 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.