Page MenuHomeFreeBSD

Pass resize parameter to vm_map_entry_resize_free
ClosedPublic

Authored by dougm on May 22 2019, 4:33 PM.
Tags
None
Referenced Files
F169784843: D20356.id57704.diff
Wed, Sep 2, 1:40 PM
F169773036: D20356.id57704.diff
Wed, Sep 2, 12:52 PM
F169663402: D20356.id57700.diff
Wed, Sep 2, 5:32 AM
F169544574: D20356.id.diff
Tue, Sep 1, 9:18 PM
Unknown Object (File)
Tue, Sep 1, 10:20 AM
Unknown Object (File)
Mon, Aug 31, 6:32 PM
Unknown Object (File)
Mon, Aug 31, 6:23 PM
Unknown Object (File)
Mon, Aug 31, 4:53 PM
Subscribers

Details

Summary

This is a small piece broken off of the change under review at D19826. Passing a parameter to vm_map_entry_resize_free that describes the amount of resizing reduces the number of functions changing the vm_map invariants regarding the max_free field of map entries.

Test Plan

I've tested with a test program that pounds the vm_map and seen no obvious performance impact from this change.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Other than the note about if()s, this looks fine.

vm_map.c
4325

I find this nesting of if()s cleaner than repeated condition in your variant. It is clear that we do some cleanup, and the kind of cleanup depends on gap_deleted.

Restore indentation. Wrap long line.

vm_map.c
4353

Did you delete the wrong line?

Fix the conflict with the old patch correctly, this time.

dougm added inline comments.
vm_map.c
4353

Yep.

kib added inline comments.
vm_map.c
1254

I think the type should be vm_size_t but I see that I myself used it inconsistently.

This revision is now accepted and ready to land.May 22 2019, 5:35 PM
This revision was automatically updated to reflect the committed changes.
dougm marked an inline comment as done.