From: patchwork-bot+netdevbpf@kernel•org
To: Lorenzo Bianconi <lorenzo@kernel•org>
Cc: bpf@vger•kernel.org, pablo@netfilter•org, kadlec@netfilter•org,
davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, netfilter-devel@vger•kernel.org,
netdev@vger•kernel.org, ast@kernel•org, daniel@iogearbox•net,
andrii@kernel•org, martin.lau@linux•dev, eddyz87@gmail•com,
lorenzo.bianconi@redhat•com, toke@redhat•com, fw@strlen•de,
hawk@kernel•org, horms@kernel•org, donhunte@redhat•com,
memxor@gmail•com
Subject: Re: [PATCH v6 bpf-next 0/3] netfilter: Add the capability to offload flowtable in XDP layer
Date: Mon, 01 Jul 2024 15:10:28 +0000 [thread overview]
Message-ID: <171984662850.25774.11398044687534883438.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1719698275.git.lorenzo@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox•net>:
On Sun, 30 Jun 2024 00:26:47 +0200 you wrote:
> Introduce bpf_xdp_flow_lookup kfunc in order to perform the lookup of
> a given flowtable entry based on the fib tuple of incoming traffic.
> bpf_xdp_flow_lookup can be used as building block to offload in XDP
> the sw flowtable processing when the hw support is not available.
>
> This series has been tested running the xdp_flowtable_offload eBPF program
> on an ixgbe 10Gbps NIC (eno2) in order to XDP_REDIRECT the TCP traffic to
> a veth pair (veth0-veth1) based on the content of the nf_flowtable as soon
> as the TCP connection is in the established state:
>
> [...]
Here is the summary with links:
- [v6,bpf-next,1/3] netfilter: nf_tables: add flowtable map for xdp offload
https://git.kernel.org/bpf/bpf-next/c/89cc8f1c5f22
- [v6,bpf-next,2/3] netfilter: add bpf_xdp_flow_lookup kfunc
https://git.kernel.org/bpf/bpf-next/c/391bb6594fd3
- [v6,bpf-next,3/3] selftests/bpf: Add selftest for bpf_xdp_flow_lookup kfunc
https://git.kernel.org/bpf/bpf-next/c/c77e572d3a8c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-01 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 22:26 [PATCH v6 bpf-next 0/3] netfilter: Add the capability to offload flowtable in XDP layer Lorenzo Bianconi
2024-06-29 22:26 ` [PATCH v6 bpf-next 1/3] netfilter: nf_tables: add flowtable map for xdp offload Lorenzo Bianconi
2024-06-29 22:26 ` [PATCH v6 bpf-next 2/3] netfilter: add bpf_xdp_flow_lookup kfunc Lorenzo Bianconi
2024-06-29 22:26 ` [PATCH v6 bpf-next 3/3] selftests/bpf: Add selftest for " Lorenzo Bianconi
2024-07-01 15:10 ` patchwork-bot+netdevbpf [this message]
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=171984662850.25774.11398044687534883438.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=donhunte@redhat$(echo .)com \
--cc=eddyz87@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=fw@strlen$(echo .)de \
--cc=hawk@kernel$(echo .)org \
--cc=horms@kernel$(echo .)org \
--cc=kadlec@netfilter$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=lorenzo.bianconi@redhat$(echo .)com \
--cc=lorenzo@kernel$(echo .)org \
--cc=martin.lau@linux$(echo .)dev \
--cc=memxor@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pablo@netfilter$(echo .)org \
--cc=toke@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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