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
F169853676: D59154.diff
Wed, Sep 2, 6:45 PM
F169791371: D59154.diff
Wed, Sep 2, 2:11 PM
F169769345: D59154.diff
Wed, Sep 2, 12:33 PM
F169769102: D59154.id184922.diff
Wed, Sep 2, 12:31 PM
F169738098: D59154.id184990.diff
Wed, Sep 2, 10:28 AM
F169684682: D59154.id184922.diff
Wed, Sep 2, 7:11 AM
F169599947: D59154.id184990.diff
Wed, Sep 2, 1:02 AM
Unknown Object (File)
Tue, Sep 1, 9:04 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 76113
Build 72996: 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.