nullfs: reduce areas protected by vnode interlock in null_lock
ClosedPublic
Actions

Authored by mjg on Aug 31 2019, 9:58 AM.

Tags

None

Referenced Files

	Unknown Object (File)
	Tue, May 27, 11:00 PM

	Unknown Object (File)
	Thu, May 22, 8:40 AM

	Unknown Object (File)
	Thu, May 8, 7:00 PM

	Unknown Object (File)
	Tue, May 6, 2:28 AM

	Unknown Object (File)
	Apr 25 2025, 11:39 AM

	Unknown Object (File)
	Apr 20 2025, 11:16 AM

	Unknown Object (File)
	Apr 20 2025, 10:12 AM

	Unknown Object (File)
	Apr 19 2025, 11:11 PM

View All 63 Files

Subscribers

imp

Details

Reviewers

kib

Commits

rS351651: nullfs: reduce areas protected by vnode interlock in null_lock

Summary

Similarly to the other routine stop taking the interlock for the lower vnode. The interlock for nullfs vnode is still taken to ensure stability of ->v_data.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

mjg created this revision.Aug 31 2019, 9:58 AM

Herald added a subscriber: imp. · View Herald TranscriptAug 31 2019, 9:58 AM

Harbormaster completed remote builds in B26207: Diff 61502.Aug 31 2019, 9:58 AM

wrong diff

clear the interlock flag for the fallback case

kib accepted this revision.Aug 31 2019, 3:17 PM

This revision is now accepted and ready to land.Aug 31 2019, 3:17 PM

Closed by commit rS351651: nullfs: reduce areas protected by vnode interlock in null_lock (authored by mjg). · Explain WhySep 1 2019, 2:52 AM

This revision was automatically updated to reflect the committed changes.

mjg added a commit: rS351651: nullfs: reduce areas protected by vnode interlock in null_lock.

Revision Contents
Changeset List

Path

Size

head/

sys/

fs/

nullfs/

null_vnops.c

19 lines

Diff 61518

View Options

head/sys/fs/nullfs/null_vnops.c

nullfs: reduce areas protected by vnode interlock in null_lockClosedPublicActions