On 10/16/2017 06:21 PM, Sagi Grimberg wrote:
Lets take this one step at a time, starting with this issue.
First, there is a reason why a simple create_ctrl fails, can we isolate
exactly which call fails? Was something else going on that might have
made the simple create_ctrl fail?
We don't see any "rdma_resolve_addr failed" or "failed to connect
queue"
messages but we do see "creating I/O queues" which means that we either
failed at IO tagset allocation or initializing connect_q.
We have a missing error code assignment so can you try the following
patch:
Hi Sagi
Sorry for the late response, here is the log with your patch, let me
know if you need more test.
Hi Yi,
I was referring to the bug you reported on a simple create_ctrl failed:
https://pastebin.com/7z0XSGSd
Does it reproduce?
yes, this issue was reproduced during "git bisect" with below patch
commit 31fdf18401703df246e20fc0382ed3594e6cf8d8
Author: Sagi Grimberg <sagi@xxxxxxxxxxx>
Date: Mon Aug 28 21:40:06 2017 +0200
nvme-rdma: reuse configure/destroy_admin_queue
No need to open-code it.
Signed-off-by: Sagi Grimberg <sagi@xxxxxxxxxxx>
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-nvme
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
