Page MenuHomeFreeBSD

Add NVMe drive to NOIOB quirk list
ClosedPublic

Authored by chuck on Jan 7 2019, 3:41 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Mar 25, 3:30 AM
Unknown Object (File)
Thu, Mar 21, 1:14 PM
Unknown Object (File)
Wed, Mar 13, 3:29 AM
Unknown Object (File)
Jan 31 2024, 7:53 PM
Unknown Object (File)
Jan 29 2024, 2:13 AM
Unknown Object (File)
Jan 22 2024, 11:24 PM
Unknown Object (File)
Jan 15 2024, 9:17 PM
Unknown Object (File)
Dec 23 2023, 12:13 AM
Subscribers

Details

Summary

This is a patch from FreeBSD Bugzilla – Bug 233969

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I have no objections, if its true.

This revision is now accepted and ready to land.Jan 7 2019, 3:50 PM
In D18772#400520, @mav wrote:

I have no objections, if its true.

I don't have access to one of these devices or the spec sheet, but the Linux NVMe driver sets the quirk NVME_QUIRK_STRIPE_SIZE for this device. The Linux text associated with this quirk is:

Prefers I/O aligned to a stripe size specified in a vendor
specific Identify field.

which sounds like what the FreeBSD driver is trying to do as well. Note that the Linux driver also sets this quirk for device ID's 0x0953, 0x0a53, and 0x0a54 (i.e. same as the current driver).

This works for me. There is a newer way to cope with this, but I don't think the 4600 implements this, so this change is appropriate.

This revision was automatically updated to reflect the committed changes.
In D18772#400655, @imp wrote:

This works for me. There is a newer way to cope with this, but I don't think the 4600 implements this, so this change is appropriate.

Out of curiosity, what is the newer way?