BPF List
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: Daniel Borkmann <daniel@iogearbox.net>, martin.lau@linux.dev
Cc: pabeni@redhat.com, kuba@kernel.org, bpf@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 1/3] netkit: Allow for configuring needed_{head,tail}room
Date: Sat, 21 Dec 2024 09:23:34 +0200	[thread overview]
Message-ID: <e08ccd22-6537-41fc-9934-84b8fdc0dc3e@blackwall.org> (raw)
In-Reply-To: <20241220234658.490686-1-daniel@iogearbox.net>

On 12/21/24 01:46, Daniel Borkmann wrote:
> Allow the user to configure needed_{head,tail}room for both netkit
> devices. The idea is similar to 163e529200af ("veth: implement
> ndo_set_rx_headroom") with the difference that the two parameters
> can be specified upon device creation. By default the current behavior
> stays as is which is needed_{head,tail}room is 0.
> 
> In case of Cilium, for example, the netkit devices are not enslaved
> into a bridge or openvswitch device (rather, BPF-based redirection
> is used out of tcx), and as such these parameters are not propagated
> into the Pod's netns via peer device.
> 
> Given Cilium can run in vxlan/geneve tunneling mode (needed_headroom)
> and/or be used in combination with WireGuard (needed_{head,tail}room),
> allow the Cilium CNI plugin to specify these two upon netkit device
> creation.
> 
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Paolo Abeni <pabeni@redhat.com>
> Cc: Nikolay Aleksandrov <razor@blackwall.org>
> ---
>  v2:
>   - static struct (Jakub)
> 
>  drivers/net/netkit.c               | 66 +++++++++++++++++++-----------
>  include/uapi/linux/if_link.h       |  2 +
>  tools/include/uapi/linux/if_link.h |  2 +
>  3 files changed, 47 insertions(+), 23 deletions(-)
> 

need coffee, just acked v1 and was looking at v2.. 

Acked-by: Nikolay Aleksandrov <razor@blackwall.org>

  parent reply	other threads:[~2024-12-21  7:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 23:46 [PATCH bpf-next v2 1/3] netkit: Allow for configuring needed_{head,tail}room Daniel Borkmann
2024-12-20 23:46 ` [PATCH bpf-next v2 2/3] netkit: Add add netkit {head,tail}room to rt_link.yaml Daniel Borkmann
2024-12-21  7:23   ` Nikolay Aleksandrov
2024-12-23 18:49   ` Jakub Kicinski
2024-12-20 23:46 ` [PATCH bpf-next v2 3/3] selftests/bpf: Extend netkit tests to validate set {head,tail}room Daniel Borkmann
2024-12-21  7:24   ` Nikolay Aleksandrov
2024-12-21  7:23 ` Nikolay Aleksandrov [this message]
2024-12-23 18:48 ` [PATCH bpf-next v2 1/3] netkit: Allow for configuring needed_{head,tail}room Jakub Kicinski

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=e08ccd22-6537-41fc-9934-84b8fdc0dc3e@blackwall.org \
    --to=razor@blackwall.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kuba@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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