Messages in this thread | | | Date | Thu, 19 Jul 2018 15:42:03 +0200 | From | Christoph Hellwig <> | Subject | Re: [PATCH 0/4] Rework NVMe abort handling |
| |
On Thu, Jul 19, 2018 at 03:28:34PM +0200, Johannes Thumshirn wrote: > PCI currently is the only transport we have which is doing more than > queueing a transport reset but trying to abort the command first. > > This series brings the other transports we currently have up to the > same level.
Without even looking at the code yet: why? The nvme abort isn't very useful, and due to the lack of ordering between different queues almost harmful on fabrics. What problem do you try to solve?
| |