Page MenuHomeFreeBSD

nvme: Always set deadline to max
ClosedPublic

Authored by imp on Oct 10 2022, 2:15 AM.
Tags
None
Referenced Files
F105333487: D36920.diff
Sun, Dec 15, 1:02 AM
Unknown Object (File)
Sun, Dec 1, 3:11 AM
Unknown Object (File)
Fri, Nov 15, 8:26 PM
Unknown Object (File)
Nov 6 2024, 7:45 PM
Unknown Object (File)
Nov 6 2024, 7:35 PM
Unknown Object (File)
Oct 21 2024, 12:20 AM
Unknown Object (File)
Oct 18 2024, 12:55 PM
Unknown Object (File)
Oct 3 2024, 10:58 PM
Subscribers

Details

Summary

The deadline always needs to be valid, and not what's left over from before.
Always initialize it to maximum.

Sponsored by: Netflix

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 47770
Build 44657: arc lint + arc unit

Event Timeline

imp requested review of this revision.Oct 10 2022, 2:15 AM

Since it is under the queue lock I don't see much difference in the order, only removal of the condition makes sense to me.

This revision is now accepted and ready to land.Oct 10 2022, 1:43 PM

simplify code and re-word commit message about what's really important here.

This revision now requires review to proceed.Oct 10 2022, 10:38 PM
This revision is now accepted and ready to land.Oct 11 2022, 2:33 PM
This revision was automatically updated to reflect the committed changes.