Kristof Provost 271f146955 pf: vnet-ify pf_hashsize, pf_hashmask, pf_srchashsize and V_pf_srchashmask ... These variables are tunables, so in principle they never change at runtime. That would mean they don't need to be tracked per-vnet. However, they both can be decreased (back to their default values) if the memory allocations for their respective tables fail, and these allocations are per-vnet. That is, it's possible for a few vnets to be started and have the tuned size for the hash and srchash tables only to have later vnets fail the initial allocation and fall back to smaller allocations. That would confuse the previously created vnets (because their actual table size and size/mask variables would no longer match). Avoid this by turning these into per-vnet variables. MFC after: 1 week Sponsored by: Rubicon Communications, LLC ("Netgate")		2024-07-17 16:00:49 +02:00
..
ipfilter/netinet	netpfil: Fix typos in source code comments	2024-04-18 16:17:10 +02:00
ipfw	net: Remove unneeded NULL check for the allocated ifnet	2024-06-28 18:16:29 +08:00
pf	pf: vnet-ify pf_hashsize, pf_hashmask, pf_srchashsize and V_pf_srchashmask	2024-07-17 16:00:49 +02:00