DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Yang Ming <ming.1.yang@nokia-sbell.com>, <dev@dpdk.org>
Subject: Re: [PATCH v2] eal/linux: skip vfio for non-privileged container
Date: Fri, 16 May 2025 15:30:22 +0200	[thread overview]
Message-ID: <7e76aaa6-09c3-4721-afbb-aeb3bc9a42e2@intel.com> (raw)
In-Reply-To: <20250327075711.648-1-ming.1.yang@nokia-sbell.com>

On 3/27/2025 8:57 AM, Yang Ming wrote:
> DPDK detect vfio container according the existence of vfio
> module. But for container with non-privileged mode, there is
> possibility that no VFIO_DIR(/dev/vfio) mapping from host to
> container when host have both Intel NIC and Mellanox NIC but
> this conntainer only allocate VFs from Mellanox NIC.
> In this case, vfio kernel module has already been loaded from
> the host.
> This scenario will cause the error log occurs in DPDK primary
> process as below:
> 'EAL:   cannot open VFIO container, error 2 (No such file or
> directory)'
> 'EAL: VFIO support could not be initialized'
> Because `rte_vfio_enable()` call `rte_vfio_get_container_fd()`
> to execute `vfio_container_fd = open(VFIO_CONTAINER_PATH,
> O_RDWR);` but VFIO_CONTAINER_PATH(/dev/vfio/vfio) doesn't exist
> in this container.
> This scenario will also lead to the delay of DPDK secondary
> process because `default_vfio_cfg->vfio_enabled = 0` and
> `default_vfio_cfg->vfio_container_fd = -1`, socket error will
> be set in DPDK primary process when it sync this info to
> the secondary process.
> This patch use to skip this kind of useless detection for this
> scenario.
> 
> Signed-off-by: Yang Ming <ming.1.yang@nokia-sbell.com>

With a few code grammar fixes below,

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

> ---
>   lib/eal/linux/eal_vfio.c | 11 +++++++++++
>   1 file changed, 11 insertions(+)
> 
> diff --git a/lib/eal/linux/eal_vfio.c b/lib/eal/linux/eal_vfio.c
> index 7132e24cba..1679d29263 100644
> --- a/lib/eal/linux/eal_vfio.c
> +++ b/lib/eal/linux/eal_vfio.c
> @@ -7,6 +7,7 @@
>   #include <fcntl.h>
>   #include <unistd.h>
>   #include <sys/ioctl.h>
> +#include <dirent.h>
>   
>   #include <rte_errno.h>
>   #include <rte_log.h>
> @@ -1083,6 +1084,7 @@ rte_vfio_enable(const char *modname)
>   	/* initialize group list */
>   	int i, j;
>   	int vfio_available;
> +	DIR *dir;
>   	const struct internal_config *internal_conf =
>   		eal_get_internal_configuration();
>   
> @@ -1119,6 +1121,15 @@ rte_vfio_enable(const char *modname)
>   		return 0;
>   	}
>   
> +	/* return 0 if VFIO directory not exist for container with non-privileged mode */

/* VFIO directory might not exist (e.g. unprivileged containers) */

> +	dir = opendir(VFIO_DIR);
> +	if (dir == NULL) {
> +		EAL_LOG(DEBUG,

"VFIO directory does not exist, skipping VFIO support..."

> +			"VFIO directory not exist, skipping VFIO support...");
> +		return 0;
> +	}
> +	closedir(dir);
> +
>   	if (internal_conf->process_type == RTE_PROC_PRIMARY) {
>   		if (vfio_mp_sync_setup() == -1) {
>   			default_vfio_cfg->vfio_container_fd = -1;


-- 
Thanks,
Anatoly

      parent reply	other threads:[~2025-05-16 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17  7:28 [PATCH] Skip vfio in the scenario of non-privileged mode Yang Ming
2025-01-17 16:47 ` Stephen Hemminger
2025-01-22  8:15   ` Yang Ming
2025-02-26  3:10     ` Yang Ming
2025-02-26 13:45     ` Stephen Hemminger
2025-02-28  5:23       ` Yang Ming
2025-03-27  7:57 ` [PATCH v2] eal/linux: skip vfio for non-privileged container Yang Ming
2025-05-16  6:46   ` David Marchand
2025-05-16 11:08     ` Moses Young
2025-05-16 13:30   ` Burakov, Anatoly [this message]

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=7e76aaa6-09c3-4721-afbb-aeb3bc9a42e2@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=ming.1.yang@nokia-sbell.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).