From: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
To: David Aldrich <david.aldrich.ntml@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>, users <users@dpdk.org>
Subject: Re: Unable to build igb_uio
Date: Mon, 29 Jul 2024 14:27:20 +0300 [thread overview]
Message-ID: <CAAFk=6C4pxn8oSWrcKeu8J+Tnto4_vPSi77DeO_TrM3Lg=191g@mail.gmail.com> (raw)
In-Reply-To: <CAJK_iej5+v3XLkvRpdLBZiBKqn0A_Br47nNiHKNMOh-nfyn10w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
Yes, it is required, replace igb_uio with vfio-pci,
I'd recommend reading this doc
https://doc.dpdk.org/guides/linux_gsg/linux_drivers.html#linux-gsg-binding-kernel
On Mon, Jul 29, 2024 at 2:02 PM David Aldrich <david.aldrich.ntml@gmail.com>
wrote:
> Hi Stephen and Oleksandr
>
> Thanks for your replies.
>
> I guess the documentation I'm looking at is out-of-date, but the
> Broadcom app note I'm looking at suggests testing with testpmd, but
> first binding with:
>
> usertools/dpdk-devbind.py -b igb_uio <PCI Device ID>
>
> Given igb_uio is deprecated, is this binding step still required and,
> if so, what parameters are now required?
>
> Best regards
> David
>
> On Fri, Jul 26, 2024 at 6:30 PM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> >
> > On Fri, 26 Jul 2024 16:04:07 +0100
> > David Aldrich <david.aldrich.ntml@gmail.com> wrote:
> >
> > > Hi
> > > I am using DPDK 23.11.1. I need to build and install linux kernel
> > > module igb_uio.
> >
> > Are you sure? igb_uio has been deprecated in favor of vfio_pci.
> > Unless you are on a really old kernel, there is no longer a need for
> igb_uio.
>
[-- Attachment #2: Type: text/html, Size: 1841 bytes --]
next prev parent reply other threads:[~2024-07-29 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 15:04 David Aldrich
2024-07-26 16:21 ` Oleksandr Nahnybida
2024-07-26 17:30 ` Stephen Hemminger
2024-07-29 11:02 ` David Aldrich
2024-07-29 11:27 ` Oleksandr Nahnybida [this message]
2024-07-29 13:06 ` David Aldrich
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='CAAFk=6C4pxn8oSWrcKeu8J+Tnto4_vPSi77DeO_TrM3Lg=191g@mail.gmail.com' \
--to=oleksandrn@interfacemasters.com \
--cc=david.aldrich.ntml@gmail.com \
--cc=stephen@networkplumber.org \
--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).