Searched hist:"3 f3e4f3c7472640aab998612a2253da95102345a" (Results 1 – 4 of 4) sorted by relevance
| /freebsd/sys/netpfil/ipfw/ |
| H A D | dn_aqm_pie.c | diff 3f3e4f3c7472640aab998612a2253da95102345a Thu Jan 27 11:41:21 CET 2022 Kristof Provost <kp@FreeBSD.org> dummynet: don't use per-vnet locks to protect global data.
The ref_count counter is global (i.e. not per-vnet) so we can't use a
per-vnet lock to protect it. Moreover, in callouts curvnet is not set,
so we'd end up panicing when trying to use DN_BH_WLOCK().
Instead we use the global sched_lock, which is already used when
evaluating ref_count (in unload_dn_aqm()).
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential Revision: https://reviews.freebsd.org/D34059
|
| H A D | ip_dn_private.h | diff 3f3e4f3c7472640aab998612a2253da95102345a Thu Jan 27 11:41:21 CET 2022 Kristof Provost <kp@FreeBSD.org> dummynet: don't use per-vnet locks to protect global data.
The ref_count counter is global (i.e. not per-vnet) so we can't use a
per-vnet lock to protect it. Moreover, in callouts curvnet is not set,
so we'd end up panicing when trying to use DN_BH_WLOCK().
Instead we use the global sched_lock, which is already used when
evaluating ref_count (in unload_dn_aqm()).
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential Revision: https://reviews.freebsd.org/D34059
|
| H A D | dn_sched_fq_pie.c | diff 3f3e4f3c7472640aab998612a2253da95102345a Thu Jan 27 11:41:21 CET 2022 Kristof Provost <kp@FreeBSD.org> dummynet: don't use per-vnet locks to protect global data.
The ref_count counter is global (i.e. not per-vnet) so we can't use a
per-vnet lock to protect it. Moreover, in callouts curvnet is not set,
so we'd end up panicing when trying to use DN_BH_WLOCK().
Instead we use the global sched_lock, which is already used when
evaluating ref_count (in unload_dn_aqm()).
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential Revision: https://reviews.freebsd.org/D34059
|
| H A D | ip_dummynet.c | diff 3f3e4f3c7472640aab998612a2253da95102345a Thu Jan 27 11:41:21 CET 2022 Kristof Provost <kp@FreeBSD.org> dummynet: don't use per-vnet locks to protect global data.
The ref_count counter is global (i.e. not per-vnet) so we can't use a
per-vnet lock to protect it. Moreover, in callouts curvnet is not set,
so we'd end up panicing when trying to use DN_BH_WLOCK().
Instead we use the global sched_lock, which is already used when
evaluating ref_count (in unload_dn_aqm()).
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential Revision: https://reviews.freebsd.org/D34059
|