vm: stop passing M_ZERO when allocating radix nodes
ClosedPublic
Actions

Authored by mjg on Jun 24 2018, 7:16 AM.

Tags

None

Referenced Files

	Unknown Object (File)
	Feb 13 2024, 3:15 PM

	Unknown Object (File)
	Dec 22 2023, 10:15 PM

	Unknown Object (File)
	Sep 6 2023, 10:18 AM

	Unknown Object (File)
	Sep 6 2023, 10:12 AM

	Unknown Object (File)
	Sep 6 2023, 10:08 AM

	Unknown Object (File)
	Sep 1 2023, 7:56 AM

	Unknown Object (File)
	Aug 26 2023, 11:29 AM

	Unknown Object (File)
	Jul 6 2023, 6:29 PM

View All 20 Files

Subscribers

imp

Details

Reviewers

alc
markj
jeff

Commits

rS335600: vm: stop passing M_ZERO when allocating radix nodes

Summary

The three leading fields are explicitely initialized and the rest is supposed to be already zeroed.

This removes one of the most common calls to memset.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

mjg created this revision.Jun 24 2018, 7:16 AM

Herald added a subscriber: imp. · View Herald TranscriptJun 24 2018, 7:16 AM

Harbormaster completed remote builds in B17582: Diff 44375.Jun 24 2018, 7:16 AM

I would add a debug-only dtor which verifies that the child pointers are zeroed.

This revision is now accepted and ready to land.Jun 24 2018, 12:37 PM

There is one already and it can be seen in the diff: vm_radix_node_zone_dtor

Closed by commit rS335600: vm: stop passing M_ZERO when allocating radix nodes (authored by mjg). · Explain WhyJun 24 2018, 1:08 PM

This revision was automatically updated to reflect the committed changes.

Nice change.

Revision Contents
Changeset List

Path

Size

head/

sys/

vm/

vm_radix.c

14 lines

Diff 44389

View Options

vm: stop passing M_ZERO when allocating radix nodesClosedPublicActions