[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174070615474.1621364.16941794449284060101.git-patchwork-notify@kernel.org>
Date: Fri, 28 Feb 2025 01:29:14 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Daniel Borkmann <daniel@...earbox.net>
Cc: kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/2] geneve: Allow users to specify source port
range
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 26 Feb 2025 19:20:29 +0100 you wrote:
> Recently, in case of Cilium, we run into users on Azure who require to use
> tunneling for east/west traffic due to hitting IPAM API limits for Kubernetes
> Pods if they would have gone with publicly routable IPs for Pods. In case
> of tunneling, Cilium supports the option of vxlan or geneve. In order to
> RSS spread flows among remote CPUs both derive a source port hash via
> udp_flow_src_port() which takes the inner packet's skb->hash into account.
> For clusters with many nodes, this can then hit a new limitation [0]: Today,
> the Azure networking stack supports 1M total flows (500k inbound and 500k
> outbound) for a VM. [...] Once this limit is hit, other connections are
> dropped. [...] Each flow is distinguished by a 5-tuple (protocol, local IP
> address, remote IP address, local port, and remote port) information. [...]
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] geneve: Allow users to specify source port range
https://git.kernel.org/netdev/net-next/c/e1f95b1992b8
- [net-next,v2,2/2] geneve, specs: Add port range to rt_link specification
https://git.kernel.org/netdev/net-next/c/5a41a00cd5d5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists