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

	F163144149: D33538.id100890.diff
	Mon, Jul 20, 12:11 PM

	F163132281: D33538.id.diff
	Mon, Jul 20, 9:14 AM

	F163104218: D33538.diff
	Mon, Jul 20, 3:03 AM

	Unknown Object (File)
	Sun, Jul 19, 2:42 AM

	Unknown Object (File)
	Sun, Jul 5, 11:56 PM

	Unknown Object (File)
	Sat, Jul 4, 9:35 PM

	Unknown Object (File)
	Wed, Jun 24, 10:35 PM

	Unknown Object (File)
	Wed, Jun 24, 1:18 PM

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