protocols: don't execute protosw_init() for every VNET
ClosedPublic
Actions

Authored by glebius on Dec 17 2021, 6:56 PM.

Tags

None

Referenced Files

	F153049819: D33538.diff
	Sat, Apr 18, 8:31 PM

	F152976069: D33538.id.diff
	Sat, Apr 18, 10:42 AM

	Unknown Object (File)
	Thu, Apr 9, 8:58 PM

	Unknown Object (File)
	Thu, Apr 9, 7:15 PM

	Unknown Object (File)
	Sat, Apr 4, 10:09 AM

	Unknown Object (File)
	Wed, Mar 25, 6:24 PM

	Unknown Object (File)
	Mar 2 2026, 5:18 AM

	Unknown Object (File)
	Feb 14 2026, 1:31 AM

View All Files

Subscribers

imp

Details

Reviewers

None

Group Reviewers

network

Commits

rG340c7343f4e0: protocols: don't execute protosw_init() for every VNET

Summary

The function now modifies pr_usrreqs only, which are always
global. Rename it to pr_usrreqs_init().

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

glebius created this revision.Dec 17 2021, 6:56 PM

Herald added a subscriber: imp. · View Herald TranscriptDec 17 2021, 6:56 PM

glebius requested review of this revision.Dec 17 2021, 6:56 PM

glebius added a parent revision: D33537: protocols: init with standard SYSINIT(9) or VNET_SYSINIT.

Harbormaster completed remote builds in B43444: Diff 100225.Dec 17 2021, 6:56 PM

glebius added a child revision: D33539: netipsec: use SYSINIT(9) instead of dom_init/dom_destroy.Dec 17 2021, 6:57 PM

This revision was not accepted when it landed; it landed in state Needs Review.Jan 3 2022, 6:23 PM

Closed by commit rG340c7343f4e0: protocols: don't execute protosw_init() for every VNET (authored by glebius). · Explain Why

This revision was automatically updated to reflect the committed changes.

glebius added a commit: rG340c7343f4e0: protocols: don't execute protosw_init() for every VNET.

Revision Contents
Changeset List

Path

Size

sys/

kern/

uipc_domain.c

8 lines

Diff 100890

View Options

protocols: don't execute protosw_init() for every VNETClosedPublicActions