From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass (mailfrom) smtp.mailfrom=kernel.org (client-ip=2600:3c04::f03c:95ff:fe5e:7468; helo=tor.source.kernel.org; envelope-from=patchwork-bot+netdevbpf@kernel.org; receiver=) Authentication-Results: mail.toke.dk; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=MXepqXaR Received: from tor.source.kernel.org (tor.source.kernel.org [IPv6:2600:3c04::f03c:95ff:fe5e:7468]) by mail.toke.dk (Postfix) with ESMTPS id 30C78AFAD5A for ; Fri, 21 Feb 2025 02:40:12 +0100 (CET) Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id 31A72683B8 for ; Fri, 21 Feb 2025 01:40:08 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 87720C4CEE2 for ; Fri, 21 Feb 2025 01:40:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1740102009; bh=btDMxeNfHBPNti2EoCCt/T314QWXygFwMOmYrLNf9ro=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=MXepqXaRM4dVPsZFOEB7ouyCJSGm2Meq4q/xIOE+jd15D6NGJv5MlJ11lOtELov26 vb6Qo/vCHwGaWuM6j+aECkThrTXqJuj9n4Co8AF/jGKjsrhioPuVmOveu2YTkIbu8Q wk8fBvXTzPE9xVv3mHz9ZKEHZsm4VYbRYMV3C/tftMDf4OyJPnoTk9+/nJmJOcmIN5 qTPKkOO8pMG98R/rr+JkAKcE2wHkRz5SR+PgOMhg28NxWpGz07teN/RQ+DsvRHUrxj JHI03CieeTQBe9pXC9MrKEU1Ekw0EKKEd1dz/sbBXjosAXPCXyksjvP1fO+R97RMjj Gwyk8ilUJvQFA== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id 71AB6380CEE2; Fri, 21 Feb 2025 01:40:41 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: patchwork-bot+netdevbpf@kernel.org Message-Id: <174010204026.1539943.5735764109259382582.git-patchwork-notify@kernel.org> Date: Fri, 21 Feb 2025 01:40:40 +0000 References: <20250216093430.957880-1-yoong.siang.song@intel.com> In-Reply-To: <20250216093430.957880-1-yoong.siang.song@intel.com> To: Song Yoong Siang Message-ID-Hash: FFPFDXWIVSNDC4BP74QHNYK4C47TBIJA X-Message-ID-Hash: FFPFDXWIVSNDC4BP74QHNYK4C47TBIJA X-MailFrom: patchwork-bot+netdevbpf@kernel.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, horms@kernel.org, willemb@google.com, florian.bezdeka@siemens.com, donald.hunter@gmail.com, corbet@lwn.net, bjorn@kernel.org, magnus.karlsson@intel.com, maciej.fijalkowski@intel.com, jonathan.lemon@gmail.com, andrew+netdev@lunn.ch, ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com, jdamato@fastly.com, sdf@fomichev.me, xuanzhuo@linux.alibaba.com, almasrymina@google.com, danielj@nvidia.com, andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com, martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org, haoluo@google.com, jolsa@kernel.org, shuah@kernel.org, alexandre.torgue@foss.st.com, joabreu@synopsys.com, mcoquelin.stm32@gmail.com, anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com, faizal.abdul.rahim@linux.intel.com, yong.liang.choong@linux.intel.com, zdenek.bouska@siemens.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, bpf@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, intel-wired-lan@lists.osuosl.org, xdp-hints@xdp-project.net X-Mailman-Version: 3.3.10 Precedence: list Subject: [xdp-hints] Re: [PATCH bpf-next v12 0/5] xsk: TX metadata Launch Time support List-Id: XDP hardware hints design discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Hello: This series was applied to bpf/bpf-next.git (net) by Martin KaFai Lau : On Sun, 16 Feb 2025 17:34:25 +0800 you wrote: > This series expands the XDP TX metadata framework to allow user > applications to pass per packet 64-bit launch time directly to the kernel > driver, requesting launch time hardware offload support. The XDP TX > metadata framework will not perform any clock conversion or packet > reordering. > > Please note that the role of Tx metadata is just to pass the launch time, > not to enable the offload feature. Users will need to enable the launch > time hardware offload feature of the device by using the respective > command, such as the tc-etf command. > > [...] Here is the summary with links: - [bpf-next,v12,1/5] xsk: Add launch time hardware offload support to XDP Tx metadata https://git.kernel.org/bpf/bpf-next/c/ca4419f15abd - [bpf-next,v12,2/5] selftests/bpf: Add launch time request to xdp_hw_metadata https://git.kernel.org/bpf/bpf-next/c/6164847e5403 - [bpf-next,v12,3/5] net: stmmac: Add launch time support to XDP ZC https://git.kernel.org/bpf/bpf-next/c/04f64dea1364 - [bpf-next,v12,4/5] igc: Refactor empty frame insertion for launch time support https://git.kernel.org/bpf/bpf-next/c/f9b53bb13923 - [bpf-next,v12,5/5] igc: Add launch time support to XDP ZC https://git.kernel.org/bpf/bpf-next/c/d7c3a7ff7502 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html