DPDK usage discussions
 help / color / mirror / Atom feed
From: Aveer Jain <aveerj@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] net/axgbe pmd and vfio-pci
Date: Wed, 10 Apr 2019 12:19:32 -0700	[thread overview]
Message-ID: <CADnsJqhrJmuhuTvMmhAJAwj=qoLrtui_Tm5SGpxpJQq_RLs_Jg@mail.gmail.com> (raw)

Hi,



I am trying to migrate to poll-mode-driver on an AMD system, and couldn’t
get the link up until I use igb_uio module in legacy mode
(intr_mode=legacy) as suggested by the release note 7.5 in dpdk (ref:
IXA00378191
https://dpdk.readthedocs.io/en/v1.8.0/rel_notes/resolved_issues.html)

But one thing is not clear to me, the nic capabilities list MSI-x support
as well as in dmesg I see MSI-X support is enabled, then ideally, I should
not see any issue in using vfio-pci module.



Is it that the current axgbe user-space driver doesn’t support the embedded
AMD ethernet devices in my system or dpdk pmd infrastructure is expecting
something enabled/disabled on my system for it to make use of vfio-pci
driver.



Don’t want to pack too many issues in one thread, but with igb_uio driver
links come up and forwarding works fine but eal_intr_thread consumes 100%
CPU and number of interrupts for igb_uio driver are huge, so either axgbe
driver is not clearing interrupt or nic is generating interrupts at crazy
rate. Is some issue like this known with igb_uio running in
intr_mode=legacy? I am suspecting it to be an issue with igb_uio because I
gave a try it on Intel 82599 nics, there link doesn’t work with latest
mainline kernel (5.0) but works with kernel 4.4.



I am sure people would have used vfio-pci with AMD ethernet devices
successfully (Advanced Micro Devices, Inc. [AMD] Device 1458).



CPU: AMD Ryzen Embedded

Running on kernel 4.19

Distro: centos

Dpdk: 19.02



Thanks,

Aveer

                 reply	other threads:[~2019-04-10 19:19 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='CADnsJqhrJmuhuTvMmhAJAwj=qoLrtui_Tm5SGpxpJQq_RLs_Jg@mail.gmail.com' \
    --to=aveerj@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).