From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pg1-f179.google.com (mail-pg1-f179.google.com [209.85.215.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2A2502BD0B for ; Sun, 1 Mar 2026 02:09:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.215.179 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772330951; cv=none; b=BGCNptyDTvL/qMTn7nvTiVlxn0QZU3HsSlYv2Sdlynmek6erCesYpORrsF0ycLXTrtHUJqFUe9WhRWxxFJtW71eF0ryeGiz9zHupX9pB+Upx2D51IdmuNREbEQcWDlNBPBrlVGBMBPQeOxF+OoMyCiA8nbIzQw3Kwu5Zo7BYjOY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772330951; c=relaxed/simple; bh=nmjck+kOKjZmB1FJWXqaPpmSxmGesHUsdaWuOwlsKPg=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=gNkmiSTyLy+Ege/lhUfurZtvR2EvfaINosysPdnDKYYiSLRVEP2zSNz45O7mGlkQcQpfyg5YIwhbnQmxKmlpSH77gOcVR3xtzN7c7gv6DxzvRYWwAjHVGEC8gcnEjXAq+JvUEhKRDqeaLqCzPj99vjMwS6+bf8AjWEDorjdkQKU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=nIR5lI4y; arc=none smtp.client-ip=209.85.215.179 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="nIR5lI4y" Received: by mail-pg1-f179.google.com with SMTP id 41be03b00d2f7-c70bfef17a4so2032904a12.2 for ; Sat, 28 Feb 2026 18:09:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1772330949; x=1772935749; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=AyMfNNvtYFQcBOR7s/jBXeIuWrprG1bo/uQ5pMKYkgs=; b=nIR5lI4yod358/+ApGwX689I70gq5lVbgthsjubKFkd0oxlQmSN5F0Hj7X+TZzOGTV yS1BB4gu7GOBDg3staajytLw6wJgoYh6v2Ai/fkKZZd4ysRtxwPaDCUlp+lL/LQZaZaq qYC3MdjA5tdLrOWlE3PcYMQwKsrBe+0MXeL/lcDJ3AAhSl61kRr/DivAKbecuX3WsnhQ 6Q4QHS/TP3G3eAUtr9LPslo2shyX3h4r2yY4rSlYQTTEXXbkTzRF71uIBKa8cYqnc+LP vVuMWiPMRh7rpq8H8jDNI6ouwmkSp+dEny5vNa98v11rY4BnuWKWCHdr7cNbBnE7dNHz bCnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1772330949; x=1772935749; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=AyMfNNvtYFQcBOR7s/jBXeIuWrprG1bo/uQ5pMKYkgs=; b=Ta73WnBglmLz4cPvK5ksn+K0D1wGA/qxs3k7xrK8rxoYoKJgaNy1bZeif4xYMLmvPJ Nw2kEJkkdfV4O9fiHUM/Fw1N2z6V+NFZbmYCkMYWHDFJbECAPVzSQftNhhvHZSnSMCW5 ULTgoIsvlWmqAVbvq4sHk2lA/3AuAmJffSyGCkiGtemu/cvQNB1xXdpGIoBZnz5w6ruS fK2Bnxfiz7AnbAWCVIsBBwELaiHlqHM667qO9436ICyGnzNzIcPFYXgpKBWnbb5Ox56H Ykonk7KgBDscqnG7UwtA27qXuOUcrKbVxmjFNQ12zacxwFzOc1rAzjbPTyupNuGVWKqT SmUQ== X-Forwarded-Encrypted: i=1; AJvYcCX9+OTzGxNUb8tmrErX9MWKWPCFdih0p+IjR62rWgzVhl4Ah4L3MbixT89VCmFzucS6TyIHXBRTj0xx7zI=@vger.kernel.org X-Gm-Message-State: AOJu0YzPJUR8xjktWTIvZuQAetTIPR6nLI4qb6nhyOmzp7YNu8JucYhD 7NZ7mC7bv8DSUPorGg2z+GOymgNHw670OvwrBYik4hH+OxE+Y+snfW0c X-Gm-Gg: ATEYQzx188eQsc20G+5Ilak3t9evCKhWZCjBRqtqn7Mz8x/TB02w5bWqavBaq1mroAZ nd6aleObrmNd/KnaV5dP+RxDhB1Gb8MdihSsBHXCULZvpReJKFe6uDSIJU28ICzODu++jYJNTM2 TMIfO60pFtG+1cWQdRxs5vXLywoGg1ZJWBuJuxZx0HbGU865WaPJUYWqlaW0uxqHtA81wuFCPMw Fui4yV0GDM5PNU/lVU0HMpZeVi5jHtFEKo5tMlSjAooMqcaAPu0DkoMSlbIBJts9+NQUPhFMyIH p4bnObRF+wb/fT6gH+y9m7Wmjoi8fSmKTIpPGwl8Ja2Xh+Hc88aKurxgBF7UquE2MxRyhiGiszS +I+lrnUg2eG62S+FGP5Hk56KeZkpSUnAe53D6zTQtay2kSMmKeuKWtPM9xkR+Q4escQCxAm+9N1 6MavSx7roPSSGJz/n3NtpBephED7mNqvSbEOPjho34SW69g8MmaKrrAlzcf5xXwUrzPTmgJ/I= X-Received: by 2002:a05:6a20:db0e:b0:361:28dd:a9ff with SMTP id adf61e73a8af0-395c3ae3de4mr6854064637.38.1772330949406; Sat, 28 Feb 2026 18:09:09 -0800 (PST) Received: from KERNELXING-MC1.tencent.com ([2408:8207:1924:8520:c4ee:cef4:762c:1339]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2adfb5b22e7sm101238895ad.3.2026.02.28.18.09.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 28 Feb 2026 18:09:08 -0800 (PST) From: Jason Xing 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 Subject: [PATCH] MAINTAINERS: add RELAY entry Date: Sun, 1 Mar 2026 10:09:02 +0800 Message-Id: <20260301020902.56476-1-kerneljasonxing@gmail.com> X-Mailer: git-send-email 2.33.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: Jason Xing 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 Signed-off-by: Jason Xing --- 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 +M: Jens Axboe +M: Jason Xing +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 L: linux-kernel@vger.kernel.org -- 2.43.5