From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1]) by mail.toke.dk (Postfix) with ESMTPS id CA287A411D4 for ; Thu, 30 Nov 2023 00:10:30 +0100 (CET) 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=Zw7SoYcK Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 2DF79CE20A7; Wed, 29 Nov 2023 23:10:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 5D9FFC433CA; Wed, 29 Nov 2023 23:10:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1701299427; bh=rXWWdIwNwFR58FE7bBu6UPEyak7iQY9m/qfQbZm1gL4=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=Zw7SoYcKgvwjdvTT1EtRzHJMgI0Fu+o/xFcBsX70ecJYts+/rn+uYfFQ/KEEisNP5 oOXhRBt6so2QG6kxRum9mBUfItCp8khDERQxiqvKUN2TgdZlw+Iu18RLQ/J4gUGkRw Sgk5hlFd7ovsDtpAUgOq7vjYSriwZyM/LwGhuXOH+/S6BYwZG1aWg3kQ/k8oVxRwTz B728gPzA+ds+W+oiTOdSR+imJ5QoDbXk/PgoFJ29ptT8VsKQ+hdZWQXuYxRkttC6E7 RvOG7a+xbZ079pgyvnih1pjoIG4Bc9PVnJGZ0B1g8XcIGxUpX9pLCCQuTdMNZd3YRr BKXQ5dgBtcKIw== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 4388EDFAA84; Wed, 29 Nov 2023 23:10:27 +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: <170129942727.25575.2476044025307341580.git-patchwork-notify@kernel.org> Date: Wed, 29 Nov 2023 23:10:27 +0000 References: <20231127190319.1190813-1-sdf@google.com> In-Reply-To: <20231127190319.1190813-1-sdf@google.com> To: Stanislav Fomichev Message-ID-Hash: 675NTZKW3KCB6LRREP4Z7LYGACEEG3KD X-Message-ID-Hash: 675NTZKW3KCB6LRREP4Z7LYGACEEG3KD X-MailFrom: patchwork-bot+netdevbpf@kernel.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev, song@kernel.org, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, haoluo@google.com, jolsa@kernel.org, kuba@kernel.org, toke@kernel.org, willemb@google.com, dsahern@kernel.org, magnus.karlsson@intel.com, bjorn@kernel.org, maciej.fijalkowski@intel.com, hawk@kernel.org, yoong.siang.song@intel.com, netdev@vger.kernel.org, xdp-hints@xdp-project.net X-Mailman-Version: 3.3.8 Precedence: list Subject: [xdp-hints] Re: [PATCH bpf-next v6 00/13] xsk: TX metadata 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 (master) by Alexei Starovoitov : On Mon, 27 Nov 2023 11:03:06 -0800 you wrote: > This series implements initial TX metadata (offloads) for AF_XDP. > See patch #2 for the main implementation and mlx5/stmmac ones for the > example on how to consume the metadata on the device side. > > Starting with two types of offloads: > - request TX timestamp (and write it back into the metadata area) > - request TX checksum offload > > [...] Here is the summary with links: - [bpf-next,v6,01/13] xsk: Support tx_metadata_len https://git.kernel.org/bpf/bpf-next/c/341ac980eab9 - [bpf-next,v6,02/13] xsk: Add TX timestamp and TX checksum offload support https://git.kernel.org/bpf/bpf-next/c/48eb03dd2630 - [bpf-next,v6,03/13] tools: ynl: Print xsk-features from the sample https://git.kernel.org/bpf/bpf-next/c/9276009d35d3 - [bpf-next,v6,04/13] net/mlx5e: Implement AF_XDP TX timestamp and checksum offload https://git.kernel.org/bpf/bpf-next/c/ec706a860eba - [bpf-next,v6,05/13] net: stmmac: Add Tx HWTS support to XDP ZC https://git.kernel.org/bpf/bpf-next/c/1347b419318d - [bpf-next,v6,06/13] xsk: Document tx_metadata_len layout https://git.kernel.org/bpf/bpf-next/c/9620e956d5b5 - [bpf-next,v6,07/13] xsk: Validate xsk_tx_metadata flags https://git.kernel.org/bpf/bpf-next/c/ce59f9686e0e - [bpf-next,v6,08/13] xsk: Add option to calculate TX checksum in SW https://git.kernel.org/bpf/bpf-next/c/11614723af26 - [bpf-next,v6,09/13] selftests/xsk: Support tx_metadata_len https://git.kernel.org/bpf/bpf-next/c/df3ed0003ec4 - [bpf-next,v6,10/13] selftests/bpf: Add csum helpers https://git.kernel.org/bpf/bpf-next/c/f6642de0c3e9 - [bpf-next,v6,11/13] selftests/bpf: Add TX side to xdp_metadata https://git.kernel.org/bpf/bpf-next/c/40808a237d9c - [bpf-next,v6,12/13] selftests/bpf: Convert xdp_hw_metadata to XDP_USE_NEED_WAKEUP https://git.kernel.org/bpf/bpf-next/c/12b4b7963d3c - [bpf-next,v6,13/13] selftests/bpf: Add TX side to xdp_hw_metadata https://git.kernel.org/bpf/bpf-next/c/60523115c1b1 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html