From: Verghis Koshi <vkoshi@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: Issues with basicfwd
Date: Wed, 19 Apr 2023 17:25:45 -0700 [thread overview]
Message-ID: <CAANwsYMv1cU01xLE0_Nux5hF0nnaAQZxBdq5_D+Q16F2FJGWHA@mail.gmail.com> (raw)
In-Reply-To: <20230419172001.3060ab54@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
Yes, just realised it. Trying now with 82540, also tried with 82599,
which are both supported by DPDK.
Will update.
On Wed, Apr 19, 2023 at 5:20 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Wed, 19 Apr 2023 16:31:37 -0700
> Verghis Koshi <vkoshi@gmail.com> wrote:
>
> > Hi Stephen,
> > Thanks for the response.
> > I've tried with two virtual NICs, each bound to VFIO, as you can see
> > below.
> >
> > verghis@verghis-VirtualBox:~/dpdk-stable-22.11.1/build$
> > ../usertools/dpdk-devbind.py --status
> >
> > Network devices using DPDK-compatible driver
> > ============================================
> > 0000:00:08.0 '79c970 [PCnet32 LANCE] 2000' drv=vfio-pci unused=pcnet32
> > 0000:00:09.0 '79c970 [PCnet32 LANCE] 2000' drv=vfio-pci unused=pcnet32
>
> Pcnet32 is not a device supported by DPDK.
>
> To use DPDK with a hardware device, the DPDK library must have a driver
> for that hardware since the library interacts directly with hardware
> registers
> and rings.
>
[-- Attachment #2: Type: text/html, Size: 1528 bytes --]
prev parent reply other threads:[~2023-04-20 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 17:11 Verghis Koshi
2023-04-19 0:14 ` Verghis Koshi
2023-04-19 1:47 ` Stephen Hemminger
2023-04-19 23:31 ` Verghis Koshi
2023-04-20 0:20 ` Stephen Hemminger
2023-04-20 0:25 ` Verghis Koshi [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=CAANwsYMv1cU01xLE0_Nux5hF0nnaAQZxBdq5_D+Q16F2FJGWHA@mail.gmail.com \
--to=vkoshi@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).