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
F156456211: D34870.id105068.diff
Wed, May 13, 7:36 PM
F156456199: D34870.id104846.diff
Wed, May 13, 7:36 PM
F156455795: D34870.diff
Wed, May 13, 7:33 PM
Unknown Object (File)
Tue, Apr 28, 12:02 AM
Unknown Object (File)
Mon, Apr 20, 11:53 AM
Unknown Object (File)
Mar 28 2026, 12:20 AM
Unknown Object (File)
Mar 27 2026, 12:16 PM
Unknown Object (File)
Mar 22 2026, 12:06 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