Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aio reap noreschedule #1966

Merged
merged 3 commits into from
Dec 7, 2024
Merged

Aio reap noreschedule #1966

merged 3 commits into from
Dec 7, 2024

Conversation

gdamore
Copy link
Contributor

@gdamore gdamore commented Dec 7, 2024

fixes #

Note that the above format should be used in your git commit comments.
You agree that by submitting a PR, you have read and agreed to our
contributing guidelines.

@gdamore gdamore force-pushed the aio-reap-noreschedule branch from dedfd30 to bc5b5e2 Compare December 7, 2024 18:58
Copy link

codecov bot commented Dec 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.88%. Comparing base (61869fa) to head (71e459e).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1966      +/-   ##
==========================================
+ Coverage   81.78%   81.88%   +0.09%     
==========================================
  Files          95       95              
  Lines       24022    24065      +43     
  Branches     3200     3208       +8     
==========================================
+ Hits        19646    19705      +59     
+ Misses       4303     4286      -17     
- Partials       73       74       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

We do not want to let operations restart if we're in the process of shutting
down.  This ensures that they get a reasonable hard failure.
Probably other subsystems should get the same treatment.  We need
to basically start the process of shutting down so that subsystems
know to cease operation before we rip memory out from underneath them.

This ensures that no new operations can be started as well, once we
have begun the process of teardown.

We also enhanced the completion of sleep to avoid some extra locking
contention, since the expiration *is* the completion.

Includes a test for this case.
@gdamore gdamore force-pushed the aio-reap-noreschedule branch from bc5b5e2 to 8fa3b2a Compare December 7, 2024 19:20
Make sure *everything* is drained before proceeding all the way
to deallocation.
@gdamore gdamore force-pushed the aio-reap-noreschedule branch from b341255 to 71e459e Compare December 7, 2024 19:56
@gdamore gdamore merged commit 71e459e into main Dec 7, 2024
17 of 19 checks passed
@gdamore gdamore deleted the aio-reap-noreschedule branch December 7, 2024 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant