Page MenuHomeFreeBSD

Don't re-evaluate ALTQ kernel configuration due to events on non-ALTQ interfaces
ClosedPublic

Authored by pkelsey on Jan 22 2019, 1:55 AM.
Tags
None
Referenced Files
F106193664: D18918.diff
Thu, Dec 26, 10:47 PM
Unknown Object (File)
Tue, Dec 10, 3:14 AM
Unknown Object (File)
Thu, Nov 28, 12:06 AM
Unknown Object (File)
Wed, Nov 27, 11:59 PM
Unknown Object (File)
Nov 25 2024, 12:01 PM
Unknown Object (File)
Nov 22 2024, 9:50 PM
Unknown Object (File)
Sep 16 2024, 3:25 PM
Unknown Object (File)
Sep 9 2024, 3:20 AM
Subscribers

Details

Summary

Prior to this patch, events on interfaces that couldn't possibly be part of a PF ALTQ configuration, such as vlan(4), would trigger a copy-existing / install-new / teardown-old PF ALTQ configuration cycle. This would result in needlessly lengthy vlan(4) creation times on systems with active PF configurations that had a large number (hundreds or thousands) of queues. On such systems that also employ hundreds or thousands of vlan(4) interfaces, the time required to create those interfaces became untenable.

Test Plan

Tested with a pf.conf containing ~4k queues. vlan(4) creation times are reduced from ~200ms each to < 10ms each.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped