Question about NVMe share I/O
James R. Bergsten
jim at thebergstens.com
Wed Jul 1 09:45:20 PDT 2015
First guess is both hosts trying to share the admin queue?
-----Original Message-----
From: Linux-nvme [mailto:linux-nvme-bounces at lists.infradead.org] On Behalf
Of Keith Busch
Sent: Wednesday, July 1, 2015 9:18 AM
To: dingxiang
Cc: Keith Busch; linux-nvme at lists.infradead.org
Subject: Re: Question about NVMe share I/O
On Tue, 30 Jun 2015, dingxiang wrote:
> Hi,All
> We are now using NVMe to develop a share I/O model,the topology is
>
> |------| |------|
> |Host A| |Host B|
> |______| |______|
> \ /
> \ /
> \ |------| /
> \| nvme |/
> |______|
I think I'm missing part of the picture here. Could you explain how you
managed to get two hosts to talk to a single nvme controller. More
specifically, how are they able to safely share the admin queue and the
pci-e function's nvme registers?
> We assign one queue for every host,
> here are the details of host A and B:
>
> Host A:
> QID :2
> MSIX irq:117
> cq prp1 :0x31253530000
> sq prp1 :0x3124af30000
>
> Host B:
> QID :3
> MSIX irq:118
> cq prp1 :0x35252470000
> sq prp1 :0x3524d820000
>
> Then we run test script in both hosts,the script is :
> insmod nvme.ko
> sleep 2
> rmmod nvme
> sleep 2
>
> When the script runs after a period of time,Host B will crash in
> function "nvme_process_cq", and Host A will print "I/O Buffer error"
messages.
> We found when host B crash,the QID Host B processed is QID 2,and the
> command_id in struct "nvme_completion" is not the value allocate in
> Host B, but same as Host A , the MSIX and prp value of host B are not
change.
> My doubt is why Host B can receive Host A's nvmeq info? In my
> opinion,the queues of Host A and B are independent, should not interfere
with each other.
> Thanks!
_______________________________________________
Linux-nvme mailing list
Linux-nvme at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
More information about the Linux-nvme
mailing list