Page MenuHomeFreeBSD

Don't store shadow copies of per-process AIO limits.
ClosedPublic

Authored by jhb on Jan 10 2018, 1:23 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 13, 10:35 AM
Unknown Object (File)
Tue, Nov 12, 9:48 PM
Unknown Object (File)
Tue, Oct 29, 3:16 AM
Unknown Object (File)
Oct 22 2024, 1:10 AM
Unknown Object (File)
Oct 18 2024, 11:47 PM
Unknown Object (File)
Oct 1 2024, 1:52 PM
Unknown Object (File)
Sep 27 2024, 12:27 AM
Unknown Object (File)
Sep 26 2024, 7:55 PM
Subscribers

Details

Summary

Previously the AIO subsystem would save a snapshot of the currently
configured per-process limits the first time a process used AIO. The
process would continue to use the snapshotted limits ignoring any
changes to the global limits during the rest of its lifetime. This
change removes the snapshotted values and changes the AIO code to
always check the global values which can be toggled at runtime.
This means an administrator can now change the effective limits of
existing processes. This is more consistent with how other limits
configured via sysctl work in FreeBSD.

Test Plan
  • run AIO tests from test suite (still waiting for run with enable_unsafe=1 to complete)

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Other than the descriptions, it all LGTM.

sys/kern/vfs_aio.c
169 ↗(On Diff #37705)

You should fix the description here and on lines 174 and 178.

This revision is now accepted and ready to land.Jan 10 2018, 3:17 AM
This revision now requires review to proceed.Jan 10 2018, 9:11 PM
This revision is now accepted and ready to land.Jan 10 2018, 9:12 PM
jhb marked an inline comment as done.Jan 10 2018, 9:16 PM
jhb added inline comments.
sys/kern/vfs_aio.c
169 ↗(On Diff #37705)

Oops, yeah. I had noticed those earlier but forgotten to include them in the change. Thanks.

This revision was automatically updated to reflect the committed changes.
jhb marked an inline comment as done.