DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhou, Danny" <danny.zhou@intel.com>
To: Sachin Sharma <sharonsachin@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] How to add veth interfaces in dpdk
Date: Fri, 12 Dec 2014 15:24:44 +0000	[thread overview]
Message-ID: <DFDF335405C17848924A094BC35766CF0A9EB641@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAH-Vi3zO4UOY0OqxHC7tfSpYd0eWbt0r0bDO4Y48jdM7VXO0CQ@mail.gmail.com>

DPDK does not have PMD to support veth. I guess you might want to try to run DPDK in container, right? 
If that is the case, you have to assign a NIC's PF or VF to container to be driven by DPDK PMD.

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sachin Sharma
> Sent: Friday, December 12, 2014 9:35 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] How to add veth interfaces in dpdk
> 
> Hi all,
> 
> I have created veth interfaces using  command "sudo ip link add veth1 type
> veth peer name veth2". However, when I use command "sudo
> ./tools/igb_uio_bind.py --force --bind=igb_uio veth1" to add veth into
> dpdk. It gives me an error that "Unknown device: veth1. Please specify
> device in "bus:slot.func" format". I do not see even veth interfaces using
> command "sudo ./tools/igb_uio_bind.py --status". Is there any way that I
> can add these interfaces into dpdk?
> 
> 
> Regards,
> Sachin.

      parent reply	other threads:[~2014-12-12 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 13:34 Sachin Sharma
2014-12-12 13:41 ` Marc Sune
2014-12-12 13:57 ` Sachin Sharma
2014-12-12 14:10   ` Marc Sune
2014-12-12 15:24 ` Zhou, Danny [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=DFDF335405C17848924A094BC35766CF0A9EB641@SHSMSX104.ccr.corp.intel.com \
    --to=danny.zhou@intel.com \
    --cc=dev@dpdk.org \
    --cc=sharonsachin@gmail.com \
    /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).