DPDK usage discussions
 help / color / mirror / Atom feed
From: Satish Patel <satish.txt@gmail.com>
To: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: how to bind VF interface into dpdk
Date: Wed, 14 Sep 2022 22:30:19 -0400	[thread overview]
Message-ID: <CAPgF-frRiVtYhK6cyS8Ytsq2v2PGpF04ON5Cczm6sGXrsUtEPA@mail.gmail.com> (raw)
In-Reply-To: <PSAPR04MB5516D1636A4D162097532641D6469@PSAPR04MB5516.apcprd04.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 796 bytes --]

Hi,

 I would also check dmesg logs for any indication or warning. I had an
issue like that and it turned out to be a BIOS setting related to some nic
shared memory.

On Wed, Sep 14, 2022 at 8:30 AM Balakrishnan K <
Balakrishnan.K1@tatacommunications.com> wrote:

> Hi All,
>
>     I am trying to bind VF interface to dpdk using dpdk-devbind.py.
>
> Unable to bind getting error “cannot bind to driver uio_pci_generic”.
>
> Steps followed:
>
> 1.modprobe uio_pci_generic
>
> 2. dpdk-devbind.py -b uio_pci_generic 0000:05:00.0
>
>
>
> Also tried with vfio-pci driver not succeeded.
>
> Attaching the dpdk-devbind -s output and the error which I got.
>
>
>
> Am I missing something could any one please help on this.
>
>
>
>
>
>
>
> Regards,
>
> Bala
>

[-- Attachment #1.2: Type: text/html, Size: 2753 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 11521 bytes --]

[-- Attachment #3: image002.png --]
[-- Type: image/png, Size: 10449 bytes --]

  reply	other threads:[~2022-09-15  2:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 12:30 Balakrishnan K
2022-09-15  2:30 ` Satish Patel [this message]
2022-09-15  7:12   ` Balakrishnan K
2022-09-15  7:22 ` David Marchand

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=CAPgF-frRiVtYhK6cyS8Ytsq2v2PGpF04ON5Cczm6sGXrsUtEPA@mail.gmail.com \
    --to=satish.txt@gmail.com \
    --cc=Balakrishnan.K1@tatacommunications.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).