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
F169052021: D34870.diff
Mon, Aug 31, 6:28 AM
F169004849: D34870.id104846.diff
Mon, Aug 31, 2:51 AM
F168955204: D34870.id.diff
Sun, Aug 30, 10:54 PM
Unknown Object (File)
Sat, Aug 29, 6:38 AM
Unknown Object (File)
Sat, Aug 29, 2:47 AM
Unknown Object (File)
Fri, Aug 28, 9:35 AM
Unknown Object (File)
Thu, Aug 27, 2:41 AM
Unknown Object (File)
Tue, Aug 25, 2:57 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