All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stojaczyk, Dariusz <dariusz.stojaczyk at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: vfio multiple processes
Date: Tue, 04 Feb 2020 12:26:46 +0000	[thread overview]
Message-ID: <4beda3a3f6e243868d99e4209bab6aab@intel.com> (raw)
In-Reply-To: 242b9a2af0a343e891cb34dbce584577@intel.com

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

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 process. There's room for improvement, but the current state is probably going to 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'll 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 drives
> > using VFIO driver (even as root). Each process seems to try to access all
> > /dev/vfio/* device files and get lots of resource busy messages. Sometimes
> > one of the processes complaint it can't find the device it's been assigned 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

             reply	other threads:[~2020-02-04 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 12:26 Stojaczyk, Dariusz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-06 14:26 [SPDK] Re: vfio multiple processes Nabarro, Tom
2020-02-03  9:14 Stojaczyk, Dariusz
2020-02-01 19:04 Luse, Paul E
2020-02-01 13:59 Nabarro, Tom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4beda3a3f6e243868d99e4209bab6aab@intel.com \
    --to=spdk@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.