Page MenuHomeFreeBSD

nvme: Remove NVME_MAX_XFER_SIZE, replace inline calculation
ClosedPublic

Authored by imp on Apr 10 2022, 5:11 PM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 10 2024, 7:34 PM
Unknown Object (File)
Oct 13 2024, 1:58 PM
Unknown Object (File)
Oct 4 2024, 9:45 PM
Unknown Object (File)
Oct 2 2024, 7:16 AM
Unknown Object (File)
Oct 2 2024, 6:25 AM
Unknown Object (File)
Sep 30 2024, 10:28 PM
Unknown Object (File)
Sep 30 2024, 2:36 AM
Unknown Object (File)
Sep 17 2024, 11:02 AM
Subscribers

Details

Summary

NVME_MAX_XFER_SIZE used to be a constant (back when MAXPHYS was a
constant) to denote the smaller of MAXPHYS or the largest PRP we could
encode with our prealloation scheme. However, it's no longer constant
since MAXPHYS varies at runtime. In addition, the actual maximum is now
based on the drive's currently in use page_size, which is also a runtime
expression. As such, remove the define and expand it inline in the one
place its used still in the tree.

Sponsored by: Netflix

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable