DPDK usage discussions
 help / color / mirror / Atom feed
From: madhukar mythri <madhukar.mythri@gmail.com>
To: users <users@dpdk.org>
Subject: Issue with parsing devargs syntax on Hyper-V platforms with DPDK-21.11
Date: Wed, 2 Feb 2022 20:40:45 +0530	[thread overview]
Message-ID: <CAAUNki3Qfsn_Qe2C=8-nRKQ4Ls99htN4PrHobeeNWf0NUkjcbA@mail.gmail.com> (raw)

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

Hi,

On the Hyper-V(Azure) environment with/without Accelerated mode, we are
seeing segmentation-fault issues while running the secondary process of
DPDK with legacy syntax of arguments on DPDK-21.11 version.
Whereas the same arguments were working well till the DPDK-21.08 version,
only with the latest DPDK-21.11 this issue occurs.

Here is the EAL argument syntax to load 'net_failsafe' PMD:
   --vdev net_vdev_netvsc0,iface=s1p0 --block 032e:00:02.0

As per analysis on this, found that a new feature was introduced "Enabled
new devargs parser" in DPDK-21.11 version. As part of this new feature
found that this DPDK patch caused this issue:
https://patchwork.dpdk.org/project/dpdk/patch/1618283653-16510-6-git-send-email-xuemingl@nvidia.com/

When we remove this patch code, we do not see any issues with loading
primary/secondary processes. So, looks like an issue in identifying the new
global syntax and fallback to legacy syntax w.r.t to Hyper-V platforms.

Even we tried to give new syntax as mentioned in this patch to load this
"vdev" based bus as follows, but still seeing issues.
     -a bus=vdev,name=net_vdev_netvsc0/class=eth/driver=vdev_netvsc

Does the new syntax support the "vdev_netvsc"(Hyper-V) based PMD ? If so,
please let us know, the syntax on the same.

Thanks,
Madhukar.

[-- Attachment #2: Type: text/html, Size: 1599 bytes --]

                 reply	other threads:[~2022-02-02 15:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAAUNki3Qfsn_Qe2C=8-nRKQ4Ls99htN4PrHobeeNWf0NUkjcbA@mail.gmail.com' \
    --to=madhukar.mythri@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).