From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: applied: [PATCH common/network v2 0/3] Performance improvements for applying VLAN / QinQ zones
Date: Mon, 19 Oct 2026 22:31:53 +0200 [thread overview]
Message-ID: <179244191103.2930950.6176325642690562997.b4-ty@b4> (raw)
In-Reply-To: <20261019112640.181849-1-s.hanreich@proxmox.com>
On Mon, 19 Oct 2026 13:26:33 +0200, Stefan Hanreich wrote:
> ## Problem
>
> When creating a VLAN / QinQ zone on a non VLAN-aware bridge, the SDN config
> generation enters a code path that calls ip_link_details from PVE::IPRoute2
> repeatedly. This causes a severe slowdown when applying configurations with a
> large amount of VNets. What exacerbated this problem was that, aside from
> calling iproute2 twice, every vnet recalculated the bridge ports for its bridge
> by iterating over all existing interfaces on the host which leads to a quadratic
> increase in runtime once the SDN configuration had been applied once.
>
> [...]
Applied, thanks!
[pve-common] applied to git/pve-common.git (master)
[1/2] iproute2: restructure get_physical_bridge_ports
commit: 2f59faccaedd04183046054b4c7d5d225c9c7643
[2/2] iproute2: add helper for getting bridge port mappings
commit: 2bf886a6302daf6ddc02b2234dd234c099142c7f
[pve-network] applied to git/pve-network.git (master)
[1/1] fix #7738: zones: use pre-computed bridge port list
commit: 6e26da7b087d6b2c12f516fcf82b6cc8b8244e28
prev parent reply other threads:[~2026-10-19 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 11:26 [PATCH common/network v2 0/3] Performance improvements for applying VLAN / QinQ zones Stefan Hanreich
2026-10-19 11:26 ` [PATCH pve-common v2 1/3] iproute2: restructure get_physical_bridge_ports Stefan Hanreich
2026-10-19 11:26 ` [PATCH pve-common v2 2/3] iproute2: add helper for getting bridge port mappings Stefan Hanreich
2026-10-19 11:26 ` [PATCH pve-network v2 3/3] fix #7738: zones: use pre-computed bridge port list Stefan Hanreich
2026-10-19 20:31 ` Thomas Lamprecht [this message]
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=179244191103.2930950.6176325642690562997.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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.