[SPDK] Re: Some doubts about spdk attach nvme device

[SPDK] Re: Some doubts about spdk attach nvme device

[Cao, Gang]

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

What's the major functionalities of Process C? Is it just for control path management?

If it is for control path management, maybe you could try to use "CUSE" support and get the NVMe devices from Process A and B.

Refer to https://spdk.io/doc/nvme.html, search "Enabling cuse support for NVMe"

-----Original Message-----
From: xu_zhaoqian(a)163.com <xu_zhaoqian(a)163.com> 
Sent: Tuesday, January 4, 2022 14:29
To: spdk(a)lists.01.org
Subject: [SPDK] Re: Some doubts about spdk attach nvme device

I know what you mean, but now process A and process B must be primary, because their huge page files need to be isolated from each other. so the shm_id of process A and process B are now different，this cannot be modified.
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org

[SPDK] Re: Some doubts about spdk attach nvme device

[alex.xu]

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

The main function of process C is to read disk data without writing
At 2022-01-04 14:36:47, "Cao, Gang" <gang.cao(a)intel.com> wrote:
>What's the major functionalities of Process C? Is it just for control path management?
>
>If it is for control path management, maybe you could try to use "CUSE" support and get the NVMe devices from Process A and B.
>
>Refer to https://spdk.io/doc/nvme.html, search "Enabling cuse support for NVMe"
>
>-----Original Message-----
>From: xu_zhaoqian(a)163.com <xu_zhaoqian(a)163.com> 
>Sent: Tuesday, January 4, 2022 14:29
>To: spdk(a)lists.01.org
>Subject: [SPDK] Re: Some doubts about spdk attach nvme device
>
>I know what you mean, but now process A and process B must be primary, because their huge page files need to be isolated from each other. so the shm_id of process A and process B are now different，this cannot be modified.
>_______________________________________________
>SPDK mailing list -- spdk(a)lists.01.org
>To unsubscribe send an email to spdk-leave(a)lists.01.org
>_______________________________________________
>SPDK mailing list -- spdk(a)lists.01.org
>To unsubscribe send an email to spdk-leave(a)lists.01.org

[SPDK] Re: Some doubts about spdk attach nvme device

[xu_zhaoqian]

[-- Attachment #1: Type: text/plain, Size: 223 bytes --]

I know what you mean, but now process A and process B must be primary, because their huge page files need to be isolated from each other. so the shm_id of process A and process B are now different，this cannot be modified.

[SPDK] Re: Some doubts about spdk attach nvme device

[Cao, Gang]

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

For this scenario, as you described Primary and Secondary, you could use the Multi-Process support by Primary and Secondary processes by setting the same shm_id parameter.

Maybe here just use Process C as the primary to take over both nvme0n1 and nvme1n1 and then process A and process B as secondary to only operate nvme0n1 and nvme1n1 respectively.

-----Original Message-----
From: 徐照钱 <xu_zhaoqian(a)163.com> 
Sent: Tuesday, January 4, 2022 11:27
To: spdk(a)lists.01.org
Subject: [SPDK] Some doubts about spdk attach nvme device

Hi all, I describe a scene: 
processA(primary  --file_prefix=1) has attach nvme0n1, processB(primary --file_prefix=2) has attach nvme1n1. now processC(primary or secondry) want to attach nvme0n1 and nvme1n1 and failed, because I found that the dpdk primary process specifies --file_prefix，then the secondry process must specify the same --file_prefix. Is there any solution?
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org