DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Request to map PCI device in a secondary that uses the --block for that device
Date: Wed, 22 May 2024 10:21:48 +0300	[thread overview]
Message-ID: <20240522102148.0db4d9b6@sovereign> (raw)
In-Reply-To: <CAO8pfFkTM8YzxmYPiP=6AzMk7psLOC0AqzxMwwBeFDdbEwcq+w@mail.gmail.com>

2024-05-22 08:46 (UTC+0200), Antonio Di Bacco:
> Is it correct that a primary requests a secondary to map a device that
> the secondary explicitly blocks with the --block arg ?
> 
> IN my case this requests of mapping creates a crash in the secondary.
> 
> Using DPDK 21.11
> 
> Best regards,
> Antonio.

Hi Antonio,

"Secondary processes which requires access to physical devices in Primary
process, must be passed with the same allow and block options."

https://doc.dpdk.org/guides/prog_guide/multi_proc_support.html

  reply	other threads:[~2024-05-22  7:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22  6:46 Antonio Di Bacco
2024-05-22  7:21 ` Dmitry Kozlyuk [this message]
2024-05-22  8:06   ` Antonio Di Bacco
2024-05-22 17:03     ` Antonio Di Bacco
2024-05-22 17:09       ` Antonio Di Bacco

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=20240522102148.0db4d9b6@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=a.dibacco.ks@gmail.com \
    --cc=users@dpdk.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 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).