All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Robin Jarry <rjarry@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH dpdk v2 0/3] net/tap: add network namespace support
Date: Mon, 27 Oct 2025 14:55:55 -0700	[thread overview]
Message-ID: <20251027145555.18fd3b01@phoenix> (raw)
In-Reply-To: <20251027181926.489642-5-rjarry@redhat.com>

On Mon, 27 Oct 2025 19:19:27 +0100
Robin Jarry <rjarry@redhat.com> wrote:

> The TAP driver currently uses ioctl operations which are name-based and
> namespace-unaware. When an interface is moved to another namespace, the
> driver loses control and cannot track the device.
> 
> This series migrates to netlink-based interface control using ifindex
> instead of names, making operations namespace-safe. When an interface
> moves to another namespace, the driver detects RTM_DELLINK, queries the
> new namespace using TUNGETDEVNETNS, and recreates netlink sockets in
> that namespace to maintain control.
> 
> The implementation falls back to ioctl when netlink is unavailable,
> preserving compatibility with older kernels.
> 
> Tested by moving TAP interfaces between namespaces while running
> testpmd. All link operations continue to work transparently after
> namespace changes.
> 
> v2: completely removed ioctl-based implementation
> 
> Robin Jarry (3):
>   net/tap: add netlink helpers
>   net/tap: replace ioctl with netlink
>   net/tap: detect namespace change
> 
>  drivers/net/tap/rte_eth_tap.c | 412 +++++++++++++++++++---------------
>  drivers/net/tap/rte_eth_tap.h |   5 +-
>  drivers/net/tap/tap_netlink.c | 291 ++++++++++++++++++++++++
>  drivers/net/tap/tap_netlink.h |  10 +-
>  4 files changed, 534 insertions(+), 184 deletions(-)
> 

Any documentation or release notes?

  parent reply	other threads:[~2025-10-27 21:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 15:37 [PATCH dpdk 0/4] net/tap: add network namespace support Robin Jarry
2025-10-27 15:37 ` [PATCH dpdk 1/4] net/tap: add netlink helpers Robin Jarry
2025-10-27 15:37 ` [PATCH dpdk 2/4] net/tap: rename internal ioctl wrapper Robin Jarry
2025-10-27 15:37 ` [PATCH dpdk 3/4] net/tap: use netlink if possible Robin Jarry
2025-10-27 16:06   ` Stephen Hemminger
2025-10-27 16:10     ` Robin Jarry
2025-10-27 16:58       ` Stephen Hemminger
2025-10-27 15:37 ` [PATCH dpdk 4/4] net/tap: detect namespace change Robin Jarry
2025-10-27 18:19 ` [PATCH dpdk v2 0/3] net/tap: add network namespace support Robin Jarry
2025-10-27 18:19   ` [PATCH dpdk v2 1/3] net/tap: add netlink helpers Robin Jarry
2025-10-27 18:19   ` [PATCH dpdk v2 2/3] net/tap: replace ioctl with netlink Robin Jarry
2025-10-27 18:19   ` [PATCH dpdk v2 3/3] net/tap: detect namespace change Robin Jarry
2025-10-27 21:55   ` Stephen Hemminger [this message]
2025-10-27 22:16 ` [PATCH dpdk v3 0/3] net/tap: add network namespace support Robin Jarry
2025-10-27 22:16   ` [PATCH dpdk v3 1/3] net/tap: add netlink helpers Robin Jarry
2025-10-27 22:16   ` [PATCH dpdk v3 2/3] net/tap: replace ioctl with netlink Robin Jarry
2025-10-27 22:16   ` [PATCH dpdk v3 3/3] net/tap: detect namespace change Robin Jarry
2025-10-30 17:55 ` [PATCH dpdk v4 0/4] net/tap: add network namespace support Robin Jarry
2025-10-30 17:55   ` [PATCH dpdk v4 1/4] net/tap: add netlink helpers Robin Jarry
2025-10-30 17:55   ` [PATCH dpdk v4 2/4] net/tap: replace ioctl with netlink Robin Jarry
2025-10-30 17:55   ` [PATCH dpdk v4 3/4] net/tap: detect namespace change Robin Jarry
2025-10-30 17:55   ` [PATCH dpdk v4 4/4] net/tap: configure link carrier Robin Jarry
2025-10-30 18:13   ` [PATCH dpdk v4 0/4] net/tap: add network namespace support Stephen Hemminger

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=20251027145555.18fd3b01@phoenix \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=rjarry@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.