From: Bernd Schubert <bschubert@ddn.com>
To: "Miklos Szeredi" <miklos@szeredi.hu>,
"Vivek Goyal" <vgoyal@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>
Cc: linux-fsdevel@vger.kernel.org,
Joanne Koong <joannelkoong@gmail.com>,
Josef Bacik <josef@toxicpanda.com>,
Bernd Schubert <bschubert@ddn.com>
Subject: [PATCH v2 0/4] fuse: Improve ftraces, per-cpu req unique and code dup removal
Date: Thu, 03 Apr 2025 15:05:05 +0200 [thread overview]
Message-ID: <20250403-fuse-io-uring-trace-points-v2-0-bd04f2b22f91@ddn.com> (raw)
This series is mainly about improved ftraces to determine
latencies between queues and also to be able to create
latency histograms - the request unique was missing in
trace_fuse_request_send so far.
Some preparation patches are added before.
Scripts to enabled tracing and to get histograms are here
https://github.com/libfuse/libfuse/pull/1186
Signed-off-by: Bernd Schubert <bschubert@ddn.com>
---
Changes in v2:
- EDITME: describe what is new in this series revision.
- EDITME: use bulletpoints and terse descriptions.
- Link to v1: https://lore.kernel.org/r/20250402-fuse-io-uring-trace-points-v1-0-11b0211fa658@ddn.com
---
Bernd Schubert (4):
fuse: Make the fuse unique value a per-cpu counter
fuse: Set request unique on allocation
fuse: {io-uring} Avoid _send code dup
fuse: fine-grained request ftraces
fs/fuse/dev.c | 37 ++++++++++------------------------
fs/fuse/dev_uring.c | 44 ++++++++++++++++------------------------
fs/fuse/fuse_dev_i.h | 4 ----
fs/fuse/fuse_i.h | 23 ++++++++++++++++-----
fs/fuse/fuse_trace.h | 57 +++++++++++++++++++++++++++++++++++++---------------
fs/fuse/inode.c | 1 +
fs/fuse/virtio_fs.c | 3 ---
7 files changed, 88 insertions(+), 81 deletions(-)
---
base-commit: 08733088b566b58283f0f12fb73f5db6a9a9de30
change-id: 20250402-fuse-io-uring-trace-points-690154bb72c7
Best regards,
--
Bernd Schubert <bschubert@ddn.com>
next reply other threads:[~2025-04-03 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 13:05 Bernd Schubert [this message]
2025-04-03 13:05 ` [PATCH v2 1/4] fuse: Make the fuse unique value a per-cpu counter Bernd Schubert
2025-04-03 18:27 ` Joanne Koong
2025-04-03 20:13 ` Bernd Schubert
2025-04-03 13:05 ` [PATCH v2 2/4] fuse: Set request unique on allocation Bernd Schubert
2025-04-03 13:05 ` [PATCH v2 3/4] fuse: {io-uring} Avoid _send code dup Bernd Schubert
2025-04-03 13:05 ` [PATCH v2 4/4] fuse: fine-grained request ftraces Bernd Schubert
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=20250403-fuse-io-uring-trace-points-v2-0-bd04f2b22f91@ddn.com \
--to=bschubert@ddn.com \
--cc=eperezma@redhat.com \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
/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).