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
Unknown Object (File)
Tue, Apr 2, 9:48 AM
Unknown Object (File)
Feb 5 2024, 12:39 PM
Unknown Object (File)
Jan 11 2024, 11:00 PM
Unknown Object (File)
Dec 15 2023, 11:09 AM
Unknown Object (File)
Nov 15 2023, 2:29 AM
Unknown Object (File)
Nov 8 2023, 9:35 PM
Unknown Object (File)
Nov 6 2023, 8:11 AM
Unknown Object (File)
Sep 28 2023, 11:17 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

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable