DPDK usage discussions
 help / color / mirror / Atom feed
From: yogev ch <yogevch@gmail.com>
To: Sidhant Hasija <shasija@tssg.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Error attaching dpdk ports to ovs
Date: Wed, 8 Aug 2018 14:14:28 +0300	[thread overview]
Message-ID: <CACPz_skf3h1VYA__m6BuRLVNyNGnefXNcXZT1+pW7JNDPARHAw@mail.gmail.com> (raw)
In-Reply-To: <252c1462-2086-bff3-febb-1f7c7b80b2f1@tssg.org>

What's your use case?
As you're using your own laptop, I assume you're not testing performance
and large traffic volumes right now.
If you're about functionality games you can use the '--vdev' option,
instead of compiling OVS with DPDK.
'--vdev' let you use through libpcap your machine's interfaces (from
ifconfig. i.e. eth0) or pcap files.

On Wed, Aug 8, 2018 at 1:30 PM, Sidhant Hasija <shasija@tssg.org> wrote:

> Hello dpdk-users,
>
> I am very much new to dpdk usage and development, and is eager to dive
> deep into it.
>
> My laptop has a Realtek NIC (RTL8101/2/6E), which going by the list of
> supported hardware pages is unsupported as also confirmed by the following
> error while starting ethtool application. Prior to starting the
> application, my ethernet card was successfully bound to vfio-pci module,
> and I also tested with binding to igb-uio module.
>
> EAL: Detected 4 lcore(s)
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> Number of NICs: 0
> EAL: Error - exiting with code: 1
>   Cause: No available NIC ports!
>
> Unable to move ahead due to NIC not being supported, I tried to setup ovs
> with dpdk. However, while attaching a port to ovs netdev bridge as written
> in the getting started guide, I get the following error.
>
> $ ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev
> $ ovs-vsctl add-port br0 brp1 -- set Interface  brp1 type=dpdk
> options:dpdk-devargs=0000:06:00.0
>
> 2018-08-08T10:09:33.136Z|00062|dpdk|ERR|EAL: Driver cannot attach the
> device (0000:06:00.0)
> 2018-08-08T10:09:33.136Z|00063|dpdk|ERR|EAL: No port found for device
> (0000:06:00.0)
> 2018-08-08T10:09:33.136Z|00064|netdev_dpdk|WARN|Error attaching device
> '0000:06:00.0' to DPDK
> 2018-08-08T10:09:33.136Z|00065|netdev|WARN|brp1: could not set
> configuration (Invalid argument)
>
> I tried with 2.9.2 and dpdk 17.11.0, as well with dpdk 18 and ovs master
> (2.10).
>
> I think the problem here is that I am trying to attach a physical
> interface to ovs bridge using its PCI address which is either not present
> or unsupported.
>
> It will be really helpful if you can please provide inputs on how to use
> dpdk without a physical interface and the direction to troubleshoot above
> ovs error. I dont have any specific use-case as yet, but just want to dive
> deep into dpdk and start learning.
>
> Many Thanks,
> Sidhant Hasija
>
>
>

      reply	other threads:[~2018-08-08 11:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 10:30 Sidhant Hasija
2018-08-08 11:14 ` yogev ch [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=CACPz_skf3h1VYA__m6BuRLVNyNGnefXNcXZT1+pW7JNDPARHAw@mail.gmail.com \
    --to=yogevch@gmail.com \
    --cc=shasija@tssg.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).