Page MenuHomeFreeBSD

nvme: limit I/O queue trackers to Identify MAXCMD
AcceptedPublic

Authored by seuros on Mon, Aug 24, 6:20 PM.
Tags
None
Referenced Files
F170592157: D59154.id184922.diff
Sat, Sep 5, 1:32 PM
F170562696: D59154.diff
Sat, Sep 5, 10:28 AM
F170544644: D59154.id.diff
Sat, Sep 5, 8:19 AM
F170543461: D59154.diff
Sat, Sep 5, 8:10 AM
F170542634: D59154.diff
Sat, Sep 5, 8:05 AM
F170516313: D59154.id184990.diff
Sat, Sep 5, 4:54 AM
F170494784: D59154.id184922.diff
Sat, Sep 5, 2:28 AM
F170456549: D59154.id184990.diff
Fri, Sep 4, 10:12 PM
Subscribers

Details

Summary

MAXCMD is the maximum number of commands the controller processes at
one time for a particular I/O queue. Allocating more trackers than
that only queues commands inside the controller. Controllers
reporting 0 are unaffected.

Approved by: ngie (co-mentor)

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 76059
Build 72942: arc lint + arc unit

Event Timeline

imp added inline comments.
sys/dev/nvme/nvme_ctrlr.c
200

This printf should be behind bootverbose, I think.

This revision is now accepted and ready to land.Tue, Aug 25, 6:57 PM
sys/dev/nvme/nvme_ctrlr.c
200

I tested it with around 30 models, but not all.

I want to keep it like this for few weeks so we can identify the disks that are quirky.

After that we can remove it or guard it.

sys/dev/nvme/nvme_ctrlr.c
200

OK.

ngie added a subscriber: ngie.

Approved by: ngie (co-mentor)

seuros marked 2 inline comments as done.