From: Sachin Sharma <sharonsachin@gmail.com>
To: dev@dpdk.org, marc.sune@bisdn.de
Subject: Re: [dpdk-dev] How to add veth interfaces in dpdk
Date: Fri, 12 Dec 2014 14:57:23 +0100 [thread overview]
Message-ID: <CAH-Vi3zOLXu1PQ3-NcDhk957pjB1UuDwRa_cUd+=5f=v6XWNRQ@mail.gmail.com> (raw)
In-Reply-To: <CAH-Vi3zO4UOY0OqxHC7tfSpYd0eWbt0r0bDO4Y48jdM7VXO0CQ@mail.gmail.com>
Hi Marc,
I have limited number of nodes (Linux nodes) in my testbed. So, I
wanted to use veth interfaces for creating some of dpdk nodes in my
nodes. You said that I can use KNI interfaces for this purpose. I am
very new to KNI terminology. Could you please redirect me to a
tutorial to create links with KNI interfaces and then adding those KNI
interfaces into dpdk?
Thanks & Regards,
Sachin.
On 12/12/14 14:34, Sachin Sharma wrote:
>* 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?
*
>veth are software interfaces, meaning there is no real NIC behind.
>That's why you cannot bind them to igb_uio.
>You can use KNI interfaces for communicating a DPDK application with the
>kernel interfaces and viceversa. There is an overhead on doing so, but
>whether this is an appropriate solution or not, depends on your use
>case. What do you plan to do?
>Marc
On Fri, Dec 12, 2014 at 2:34 PM, Sachin Sharma <sharonsachin@gmail.com>
wrote:
>
> 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.
>
next prev parent reply other threads:[~2014-12-12 13:57 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 [this message]
2014-12-12 14:10 ` Marc Sune
2014-12-12 15:24 ` Zhou, Danny
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='CAH-Vi3zOLXu1PQ3-NcDhk957pjB1UuDwRa_cUd+=5f=v6XWNRQ@mail.gmail.com' \
--to=sharonsachin@gmail.com \
--cc=dev@dpdk.org \
--cc=marc.sune@bisdn.de \
/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).