From: Stephen Hemminger <stephen@networkplumber.org>
To: "Robin Jarry" <rjarry@redhat.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH dpdk 3/4] net/tap: use netlink if possible
Date: Mon, 27 Oct 2025 09:58:47 -0700 [thread overview]
Message-ID: <20251027095847.2a1afb37@phoenix> (raw)
In-Reply-To: <DDT8HYDZ6BS5.4UGBB34IPO3I@redhat.com>
On Mon, 27 Oct 2025 17:10:24 +0100
"Robin Jarry" <rjarry@redhat.com> wrote:
> Stephen Hemminger, Oct 27, 2025 at 17:06:
> > Netlink has been available since linux 2.4!
> > Rather than having two code paths, only one of which gets tested,
> > better to commit to netlink and use it.
> >
> > Since dealing with netlink is a nuisance, I wonder if using
> > libmnl would be better. Yes, it creates new dependency but netlink
> > handling has been place with lots of Coverity overruns etc.
>
> I don't mind replacing ioctl with netlink calls but adding a libmnl
> dependency just for one driver seems overkill.
>
There is netlink handling in a couple drivers but probably not worth
bothering for now.
next prev parent reply other threads:[~2025-10-27 16:58 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 [this message]
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 ` [PATCH dpdk v2 0/3] net/tap: add network namespace support Stephen Hemminger
2025-10-27 22:16 ` [PATCH dpdk v3 " 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=20251027095847.2a1afb37@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.