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
F167954608: D34870.diff
Tue, Aug 25, 2:57 PM
F167873812: D34870.id105068.diff
Tue, Aug 25, 4:12 AM
Unknown Object (File)
Tue, Aug 25, 12:27 AM
Unknown Object (File)
Mon, Aug 24, 2:34 PM
Unknown Object (File)
Sat, Aug 22, 5:23 PM
Unknown Object (File)
Sat, Aug 22, 2:31 PM
Unknown Object (File)
Sat, Aug 22, 1:59 PM
Unknown Object (File)
Tue, Aug 11, 9:59 PM
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