Page MenuHomeFreeBSD

pfsync: Call pfsyncintr() directly from pfsync_msg_intr() rather than scheduling a swi
AbandonedPublic

Authored by kp on Nov 14 2018, 9:25 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 9 2024, 6:54 AM
Unknown Object (File)
Dec 22 2023, 11:16 PM
Unknown Object (File)
Jul 4 2023, 7:02 PM
Unknown Object (File)
Jun 25 2023, 5:31 AM
Unknown Object (File)
May 5 2023, 4:06 PM
Unknown Object (File)
Mar 17 2023, 10:53 PM
Unknown Object (File)
Mar 3 2023, 11:57 PM
Unknown Object (File)
Feb 22 2023, 8:27 AM
Subscribers

Details

Reviewers
None
Group Reviewers
network
Summary

When we're done processing a batch of pfsync_msg we can immediately
proceed to pfsyncintr(), rather than schedule a swi (possibly several
times) during the processing. This reduces the swi scheduling overhead,
and also reduces contention on PFSYNC_LOCK.

Replace pfsync_push() calls in the pfsync_msg_intr() path by simply
setting the PFSYNCF_PUSH flag, because we'll always call pfsyncintr()
later. There's no need to schedule the swi.

In pfsync_q_ins() we don't need to schedule the swi either, because it's
always called through pfsync_msg_intr(), so pfsyncint() is guaranteed to
run.

In all other cases (like when we request an update in response to a
received update) we still schedule the swi. Those flows are unmodified.

Tests show a ~25% improvement in throughput.

Sponsored by: Orange Business Services

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 20815