From: Jason Xing <kerneljasonxing@gmail.com>
To: axboe@kernel.dk, rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: [PATCH v5 0/5] relayfs: misc changes
Date: Thu, 12 Jun 2025 14:11:56 +0800 [thread overview]
Message-ID: <20250612061201.34272-1-kerneljasonxing@gmail.com> (raw)
From: Jason Xing <kernelxing@tencent.com>
The series mostly focuses on the error counters which helps every user
debug their own kernel module.
---
v5
Link: https://lore.kernel.org/all/20250610004844.66688-1-kerneljasonxing@gmail.com/
1. add Masami's reviewed-by in the first patch
2. fix the wrong printk format specifiers in patch [4/5]
v4
Link: https://lore.kernel.org/all/20250518025734.61479-1-kerneljasonxing@gmail.com/
1. add [1] as the firt/prep/clean-up commit in the series.
2. the rest four patches are not touched, compared to v4.
3. add Masami's reviewed-by tags for last four patches.
[1]: https://lore.kernel.org/all/20250507134225.63248-1-kerneljasonxing@gmail.com/
Jason Xing (5):
relayfs: abolish prev_padding
relayfs: support a counter tracking if per-cpu buffers is full
relayfs: introduce getting relayfs statistics function
blktrace: use rbuf->stats.full as a drop indicator in relayfs
relayfs: support a counter tracking if data is too big to write
drivers/gpu/drm/i915/gt/uc/intel_guc_log.c | 3 +-
drivers/net/wwan/iosm/iosm_ipc_trace.c | 3 +-
drivers/net/wwan/t7xx/t7xx_port_trace.c | 2 +-
include/linux/relay.h | 24 ++++++--
kernel/relay.c | 66 +++++++++++++++++-----
kernel/trace/blktrace.c | 22 +-------
6 files changed, 77 insertions(+), 43 deletions(-)
--
2.43.5
next reply other threads:[~2025-06-12 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 6:11 Jason Xing [this message]
2025-06-12 6:11 ` [PATCH v5 1/5] relayfs: abolish prev_padding Jason Xing
2025-06-12 6:11 ` [PATCH v5 2/5] relayfs: support a counter tracking if per-cpu buffers is full Jason Xing
2025-06-12 6:11 ` [PATCH v5 3/5] relayfs: introduce getting relayfs statistics function Jason Xing
2025-06-12 6:12 ` [PATCH v5 4/5] blktrace: use rbuf->stats.full as a drop indicator in relayfs Jason Xing
2025-06-12 6:12 ` [PATCH v5 5/5] relayfs: support a counter tracking if data is too big to write Jason Xing
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=20250612061201.34272-1-kerneljasonxing@gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=kernelxing@tencent.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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).