nvme sq associations
Quoted 6 lines · Christoph Hellwig
Honestly I'd rather not merge this whole patchset at all. It is a completly frinde feature for a totally misdesigned part of the NVMe spec. Until actual controller in the hands of prosumers support anything like that I'm very reluctant to bloat the driver fast path for it.
Thank you for the feedback.
While I agree with your remarks regarding feature design in NVMe spec the minimal implementation proposed in this patchset would help resolving the problems outlined int the original post (undesired queue sharing and noisy neighbor).
For controllers that do not support NVM sets and SQ associations the configuration would stay the same as it used to be. So I would be interested to know more about what brings your concerns for the driver fast path.
Best regards,
Andrey
_______________________________________________
Linux-nvme mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-nvme
Keith Busch
maintainerQuoted 8 lines · Andrey
Quoted 6 lines · Christoph Hellwig
Honestly I'd rather not merge this whole patchset at all. It is a completly frinde feature for a totally misdesigned part of the NVMe spec. Until actual controller in the hands of prosumers support anything like that I'm very reluctant to bloat the driver fast path for it.
Quoted 5 lines
Thank you for the feedback.
While I agree with your remarks regarding feature design in NVMe spec the minimal implementation proposed in this patchset would help resolving the problems outlined int the original post (undesired queue sharing and noisy neighbor).
You still get noisy neighbor with this approach, though: completions from one set can stall the driver from reaping another set's completions that were posted earlier.
_______________________________________________
Linux-nvme mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-nvme