From: "Asbjørn Sloth Tønnesen" <wireguard@asbjorn.st>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Asbjørn Sloth Tønnesen" <wireguard@asbjorn.st>,
wireguard@lists.zx2c4.com
Subject: [PATCH] ipc: linux: filter netdevices kernel-side
Date: Fri, 5 Sep 2025 19:51:49 +0000 [thread overview]
Message-ID: <20250905195150.1134769-1-wireguard@asbjorn.st> (raw)
Tell the kernel that we are only interested in wireguard
netdevices, so that the kernel don't have to tells us about
all the other netdevices.
Tested with 10000 netdevices (common with ISP BNG setups),
out of which 1 was a wireguard netdevice.
Baseline:
# time ./src/wg show
real 0m0.342s
user 0m0.013s
sys 0m0.290s
With patch:
# time ./src/wg show
real 0m0.006s
user 0m0.000s
sys 0m0.005s
Signed-off-by: Asbjørn Sloth Tønnesen <wireguard@asbjorn.st>
---
NB: Since this email has been on the list a long-time, then
maybe it will avoid moderation.
src/ipc-linux.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/src/ipc-linux.h b/src/ipc-linux.h
index 01247f1..c56fede 100644
--- a/src/ipc-linux.h
+++ b/src/ipc-linux.h
@@ -80,6 +80,7 @@ static int kernel_get_wireguard_interfaces(struct string_list *list)
int ret = 0;
struct nlmsghdr *nlh;
struct ifinfomsg *ifm;
+ struct nlattr *linkinfo_nest;
ret = -ENOMEM;
rtnl_buffer = calloc(SOCKET_BUFFER_SIZE, 1);
@@ -105,6 +106,11 @@ static int kernel_get_wireguard_interfaces(struct string_list *list)
nlh->nlmsg_seq = seq;
ifm = mnl_nlmsg_put_extra_header(nlh, sizeof(*ifm));
ifm->ifi_family = AF_UNSPEC;
+
+ linkinfo_nest = mnl_attr_nest_start(nlh, IFLA_LINKINFO);
+ mnl_attr_put_strz(nlh, IFLA_INFO_KIND, WG_GENL_NAME);
+ mnl_attr_nest_end(nlh, linkinfo_nest);
+
message_len = nlh->nlmsg_len;
if (mnl_socket_sendto(nl, rtnl_buffer, message_len) < 0) {
--
2.51.0
reply other threads:[~2025-09-05 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250905195150.1134769-1-wireguard@asbjorn.st \
--to=wireguard@asbjorn.st \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).