Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 08 Nov 2018 22:51:57 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 143622] [pfil] [patch] unlock pfil lock while calling firewall hooks
Message-ID:  <bug-143622-7501-dA4P8BoBXT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-143622-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-143622-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D143622

Kristof Provost <kp@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kp@freebsd.org

--- Comment #5 from Kristof Provost <kp@freebsd.org> ---
(In reply to Max Laier from comment #2)
While rmlocks are relatively lightweight there is still a non-zero overhead.
For the purposes of a test the lock can simply be removed, and without it I=
 see
~2% more packets per second in pf than with it.
I've been thinking about replacing it with a CK_LIST and epoch based cleanu=
p,
but I stopped working on it when I spotted that ipfw relies on the lock. It
should be possible to move that into ipfw, but I'm not sure the 2% is worth
that work.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-143622-7501-dA4P8BoBXT>