public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Xing <kerneljasonxing@gmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk
Cc: andriy.shevchenko@linux.intel.com, michel.dagenais@polymtl.ca,
	richardj_moore@uk.ibm.com, bob@watson.ibm.com, karim@opersys.com,
	zanussi@us.ibm.com, linux-kernel@vger.kernel.org,
	Jason Xing <kernelxing@tencent.com>
Subject: [PATCH] MAINTAINERS: add RELAY entry
Date: Sun,  1 Mar 2026 10:09:02 +0800	[thread overview]
Message-ID: <20260301020902.56476-1-kerneljasonxing@gmail.com> (raw)

From: Jason Xing <kernelxing@tencent.com>

RELAYFS was originally developed by Tom Zanussi and Karim
Yaghmour in 2005[1]. Jens Axboe converted it from filesystem
into a generic API in 2006[2] and made it widely known through
the notable I/O tracing tool blktrace. In the decade, there remain
a few users scatterred across different subsystems, like recently
added wifi commit[3] that is an example to show how to communicate
between users and kernel. Last year I've already done some
maintenance and added/corrected some diagnostic counters.

At Tencent, we internally maintain RELAY as one of most crucial
components of network observibility platform which was shared a
bit at LPC 2025[4][5] and hopefully will be published in the paper
this year. RELAY has proven highly efficient due to its inherent
design essence. This design becomes the indispensable way to build
a 7x24 platform monitoring various hot paths even without any
selectively sampling (yes, sampling is commonly used to avoid the
overall performance degradation). One of the recommended usages is
use its zerocopy function relay_reserve() to transfer data in a
raw format that can be recognized and parsed by the corresponding
application to userspace without introducing heavy locks and
complicated logic that appears in other types of approaches, like
printk. More details can be discovered by reading through the
Documentation :)

Credits are given to the all the contributors and reviewers for
RELAY/RELAYFS in the past and future! Many thanks!

[1]: commit e82894f84dbb ("[PATCH] relayfs")
[2]: commit b86ff981a825 ("[PATCH] relay: migrate from relayfs to
a generic relay API")
[3]: commit c1bf6959dd81 ("wifi: ath11k: Register relayfs entries
for CFR dump")
[4]: https://lpc.events/event/19/contributions/2055/
[5]: https://lpc.events/event/19/contributions/2010/

Acked-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Jason Xing <kernelxing@tencent.com>
---
 MAINTAINERS | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index b8d8a5c41597..5d751760136c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -22283,6 +22283,16 @@ L:	linux-wireless@vger.kernel.org
 S:	Orphan
 F:	drivers/net/wireless/rsi/
 
+RELAY
+M:	Andrew Morton <akpm@linux-foundation.org>
+M:	Jens Axboe <axboe@kernel.dk>
+M:	Jason Xing <kernelxing@tencent.com>
+L:	linux-kernel@vger.kernel.org
+S:	Maintained
+F:	Documentation/filesystems/relay.rst
+F:	include/linux/relay.h
+F:	kernel/relay.c
+
 REGISTER MAP ABSTRACTION
 M:	Mark Brown <broonie@kernel.org>
 L:	linux-kernel@vger.kernel.org
-- 
2.43.5


             reply	other threads:[~2026-03-01  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  2:09 Jason Xing [this message]
2026-03-01 13:38 ` [PATCH] MAINTAINERS: add RELAY entry Jens Axboe
2026-03-02  8:35 ` Andy Shevchenko
2026-03-02  8:40   ` Jason Xing
2026-03-02  8:47     ` Jason Xing
2026-03-02  8:54       ` Andy Shevchenko
2026-03-02  9:10         ` Jason Xing
2026-03-02  8:51     ` Andy Shevchenko

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=20260301020902.56476-1-kerneljasonxing@gmail.com \
    --to=kerneljasonxing@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=axboe@kernel.dk \
    --cc=bob@watson.ibm.com \
    --cc=karim@opersys.com \
    --cc=kernelxing@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel.dagenais@polymtl.ca \
    --cc=richardj_moore@uk.ibm.com \
    --cc=zanussi@us.ibm.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