From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-dy1-f178.google.com (mail-dy1-f178.google.com [74.125.82.178]) (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 2A79425228D for ; Tue, 27 Jan 2026 06:00:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.125.82.178 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769493632; cv=none; b=VPkdLkJy9qwaXKP8uGRyPE0ng4TmhSRHrXyGTpPbEbJyUVnTMbnaOpeO9nuJWAYaEex4UWgzFKEuW4YGIB/Nud6Ww4Y02IgMsu4UDlwRtSYpS3d9BCWoqijjlkhdVww/yoeN8ifoQ/YaCJ5wIwbq1UDexURPKRCDboYd2rGJBe8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769493632; c=relaxed/simple; bh=v/u+rBX4luP4l2y0k4d4MJwxSQLjgxjIcVpFBIL6lHQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=b7XsrpuoTDuiSHfZCjDQ3L+AWLvQlp+ZB/MR4fzRbPTss4IVd84+/ZfHqNqq4J3Z1A5/1EPk0sm5rx5XOovvfx12nXfk4lqLfPyHmtALIMVx8qq88/c+vgSZSFtADhvUgrFYxfe5Mw1R9z7V9XBs0cL5to+ej8PzHseFVJFXS7c= 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=DLDqdHPf; arc=none smtp.client-ip=74.125.82.178 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="DLDqdHPf" Received: by mail-dy1-f178.google.com with SMTP id 5a478bee46e88-2b71557299dso7553881eec.1 for ; Mon, 26 Jan 2026 22:00:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1769493630; x=1770098430; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=a803xA0SW+lSUQWToabOiMzbo1P7cUc3kCdEW2eaQec=; b=DLDqdHPfWk0o+gSD5pgARfeKHy2TUdAaS8uw1NmauBipNaULr5DL+mLTBxcMKTkjxG +w5gjtRDs8DR1RtwVb9nwlv7k+E1OtsCPJHtHONYHtT4J+xnSMPhA3VCb4CJe8ycczuL ENFpSLbU5Adck6SIVvpmOJOok+lWIPro6yf7zoPVJONnljqQkIEdVR9sALcLQ+q7EKSc 7STZ3CSGsWs21Swpq2QhkaTIzMZc1lpqNNyXJAlMWlTLoT8JYzcKcJnVJ3HzGRiSskV3 K/vIJ1pcgleYZHjGwTu/c0OxE510Mvuzwk1kpR+elyWCeiOr5GzExE5p7ak0Kr4t6Yxq EzBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1769493630; x=1770098430; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=a803xA0SW+lSUQWToabOiMzbo1P7cUc3kCdEW2eaQec=; b=EN5fiHiJDlBNjZLgRypUkzwg76D/0J18Y1UrMjz831otQ5Q+Xh9x3zoiZyEtdo106W DmcGi7NDA+q5uzEpaIy/sJqSBB5BMylsp6h8NWFisYT9UzWbTxTNIhlS0U+H5KMRCHqF iGVmHwwNc16G8CkTekWX94AvsAnJumFspZC87q+3Fh1gYcAw269j8B+X3cBF+4sjAtc5 McIf4dU/IsRavqp3PVJmI1YMwCC5Y9bxerYHHzr54BlTY9DenSD/UoyY+v9R9c77V3vZ n8RQV6MH5QqkgVqWzQPgsFN0UTLhyiLnMKGBP6YTEu/GKybQCEbd/B1QMzUus7DGDU4k NPbg== X-Forwarded-Encrypted: i=1; AJvYcCUQTpozR0Tjp7QJv1ExrVTChciw0zLyosPOQjY347XKMItaWcl3d5xMMf1df5ybbEOLJJnCMlDos4g=@vger.kernel.org X-Gm-Message-State: AOJu0YyS2K4tRIAdfcMGhJwlxIizoNEBFrWDx9peiGPq1PRgw1b/xS5/ uPKvoHvOKJY2jCVDAOWl4hRrFEBPoOjkABZQspVo7s0/m5/Ba0nAC6g= X-Gm-Gg: AZuq6aJEqKHSUTnGSw+BFRLUumGzmsQ7zxbwKjOzWcY2NYg2mrH35ImjxIBUUd3aZp1 Z9ZwKk5pc7UYtiotaa0VWuszDNXA0uiagH9fTiP0ReHq2CiFzaRzZpwDS/6yIHGUAKgG9VFYwl+ 0ORkKTf/m1G+b2eYnaFMhBIRuYMCI3vNTMmUecwXqXmpWIeKlVDZN1C12yNxNQGd88RiUBEESHF Ef6GmrFFojY+sSRDrmgGl4Usw3Vp5YHZOfQDLsVF4Jnkv25aBCjk+2AlLB1b4HkqbAkBpXE/Bu6 m1qcOCDpKdSdnkGL3gT3fFFHtwo7+s6sCv+CMO2yJ1ZtlFg14TBvRLp92VZ26IObMyojyTtEbMs qMg/Y+RGMZVReJDQYEHbsUTCLz/Qvri9EBIIGIPkjQj5y2Dhpx9QOrPAukNSVKK8GXnLZOJh2QM RxwiA9ovDIYcq2joXhx6FcjMd+O0uzpYpZZwhoa7cHY6NiVvTmWUp9TvBaPKCq9lz7VFsV4N6Bg OXwg9Pb24YUS1MT X-Received: by 2002:a05:7022:20f:b0:123:2d00:1668 with SMTP id a92af1059eb24-124a00e861emr496547c88.49.1769493629755; Mon, 26 Jan 2026 22:00:29 -0800 (PST) Received: from localhost (c-76-102-12-149.hsd1.ca.comcast.net. [76.102.12.149]) by smtp.gmail.com with ESMTPSA id a92af1059eb24-1247d90d13esm21240114c88.2.2026.01.26.22.00.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 26 Jan 2026 22:00:29 -0800 (PST) Date: Mon, 26 Jan 2026 22:00:28 -0800 From: Stanislav Fomichev To: Jakub Kicinski Cc: Bobby Eshleman , Mina Almasry , "David S. Miller" , Eric Dumazet , Paolo Abeni , Simon Horman , Kuniyuki Iwashima , Willem de Bruijn , Neal Cardwell , David Ahern , Arnd Bergmann , Jonathan Corbet , Andrew Lunn , Shuah Khan , Donald Hunter , Stanislav Fomichev , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org, asml.silence@gmail.com, matttbe@kernel.org, skhawaja@google.com, Bobby Eshleman Subject: Re: [PATCH net-next v10 0/5] net: devmem: improve cpu cost of RX token management Message-ID: References: <20260115-scratch-bobbyeshleman-devmem-tcp-token-upstream-v10-0-686d0af71978@meta.com> <20260120170749.101e8bcc@kernel.org> <20260126173124.1f0bb98e@kernel.org> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20260126173124.1f0bb98e@kernel.org> On 01/26, Jakub Kicinski wrote: > On Mon, 26 Jan 2026 10:45:22 -0800 Bobby Eshleman wrote: > > I'm onboard with improving what we have since it helps all of us > > currently using this API, though I'm not opposed to discussing a > > redesign in another thread/RFC. I do see the attraction to locating the > > core logic in one place and possibly reducing some complexity around > > socket/binding relationships. > > > > FWIW regarding nl, I do see it supports rtnl lock-free operations via > > '62256f98f244 rtnetlink: add RTNL_FLAG_DOIT_UNLOCKED' and routing was > > recently made lockless with that. I don't see / know of any fast path > > precedent. I'm aware there are some things I'm not sure about being > > relevant performance-wise, like hitting skb alloc an additional time > > every release batch. I'd want to do some minimal latency comparisons > > between that path and sockopt before diving head-first. > > FTR I'm not really pushing Netlink specifically, it may work it > may not. Perhaps some other ioctl-y thing exists. Just in general > setsockopt() on a specific socket feels increasingly awkward for > buffer flow. Maybe y'all disagree. > > I thought I'd clarify since I may be seen as "Mr Netlink Everywhere" :) >From my side, if we do a completely new uapi, my preference would be on an af_xdp like mapped rings (presumably on a netlink socket?) to completely avoid the user-kernel copies.