From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============8031252072194231825=="
MIME-Version: 1.0
From: Stojaczyk, Dariusz <dariusz.stojaczyk at intel.com>
Subject: [SPDK] Re: vfio multiple processes
Date: Tue, 04 Feb 2020 12:26:46 +0000
Message-ID: <4beda3a3f6e243868d99e4209bab6aab@intel.com>
In-Reply-To: 242b9a2af0a343e891cb34dbce584577@intel.com
List-ID: <spdk@lists.01.org>
To: spdk@lists.01.org

--===============8031252072194231825==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Ah, that's a limitation I introduced together with DPDK 18.11 support. SPDK=
 keeps vfio handles open because they may be required for a secondary proce=
ss. There's room for improvement, but the current state is probably going t=
o stay for a while.

D.

> -----Original Message-----
> From: Stojaczyk, Dariusz <dariusz.stojaczyk(a)intel.com>
> Sent: Monday, February 3, 2020 10:14 AM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: [SPDK] Re: vfio multiple processes
> =

> TBH I'm not sure the whitelist should be required. Sounds like a bug, I'l=
l take a
> look.
> =

> D.
> =

> > -----Original Message-----
> > From: Nabarro, Tom <tom.nabarro(a)intel.com>
> > Sent: Saturday, February 1, 2020 3:00 PM
> > To: Storage Performance Development Kit <spdk(a)lists.01.org>
> > Subject: [SPDK] Re: vfio multiple processes
> >
> > Resolved by adding pci whitelist into spdk_env_opts.
> > Adding whitelist into nvme.conf was not sufficient.
> >
> > Regards,
> > Tom Nabarro - DCG/ESAD
> > M: +44 (0)7786 260986
> > Skype: tom.nabarro
> >
> > From: Nabarro, Tom
> > Sent: Friday, January 31, 2020 12:42 PM
> > To: 'Storage Performance Development Kit' <spdk(a)lists.01.org>
> > Subject: vfio multiple processes
> >
> > Can't run multiple SPDK processes each accessing disjoint set of NVMe d=
rives
> > using VFIO driver (even as root). Each process seems to try to access a=
ll
> > /dev/vfio/* device files and get lots of resource busy messages. Someti=
mes
> > one of the processes complaint it can't find the device it's been assig=
ned in
> > nvme.conf.
> >
> > Have any ideas?
> > (processes are started in normal, non-multiprocess mode)
> >
> > Thanks in advance
> >
> > Best regards,
> > Tom Nabarro BEng (hons)
> > Extreme Storage Architecture & Development
> > Intel Corporation
> > E: tom.nabarro(a)intel.com<mailto:tom.nabarro(a)intel.com>
> > M: +44 (0)7786 260986
> > Skype: tom.nabarro
> >
> > ---------------------------------------------------------------------
> > Intel Corporation (UK) Limited
> > Registered No. 1134945 (England)
> > Registered Office: Pipers Way, Swindon SN3 1RJ
> > VAT No: 860 2173 47
> >
> > This e-mail and any attachments may contain confidential material for
> > the sole use of the intended recipient(s). Any review or distribution
> > by others is strictly prohibited. If you are not the intended
> > recipient, please contact the sender and delete all copies.
> > _______________________________________________
> > 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
--===============8031252072194231825==--