From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 0/2] add virtual function support to network-interface-pinning
Date: Tue, 22 Jul 2025 16:52:21 +0200 [thread overview]
Message-ID: <20250722145223.351778-1-s.hanreich@proxmox.com> (raw)
Instead of generating a .link file for every virtual function, with this patch
series proxmox-network-interface-pinning now includes a udev rule that
dynamically changes the name of virtual functions according to the pinned name
of its parent device.
pve-manager:
Stefan Hanreich (2):
configs: add udev helper for pinning virtual function names
network-interface-pinning: do not generate link files for vfs
PVE/CLI/proxmox_network_interface_pinning.pm | 9 ++++-
configs/Makefile | 4 ++-
configs/virtual-function-pinning-helper | 37 ++++++++++++++++++++
configs/virtual-function-pinning.rules | 1 +
4 files changed, 49 insertions(+), 2 deletions(-)
create mode 100644 configs/virtual-function-pinning-helper
create mode 100644 configs/virtual-function-pinning.rules
Summary over all repositories:
4 files changed, 49 insertions(+), 2 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-22 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 14:52 Stefan Hanreich [this message]
2025-07-22 14:52 ` [pve-devel] [PATCH pve-manager 1/2] configs: add udev helper for pinning virtual function names Stefan Hanreich
2025-07-22 14:52 ` [pve-devel] [PATCH pve-manager 2/2] network-interface-pinning: do not generate link files for vfs Stefan Hanreich
2025-07-23 17:31 ` [pve-devel] applied: [PATCH manager 0/2] add virtual function support to network-interface-pinning Thomas Lamprecht
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=20250722145223.351778-1-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.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.