From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "ovs-discuss@openvswitch.org" <ovs-discuss@openvswitch.org>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] OVS-DPDK - af_packet vdev configuration - Error
Date: Mon, 19 Jun 2017 13:59:06 +0000 [thread overview]
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013C1F82@FRAEML521-MBX.china.huawei.com> (raw)
Not solved - the tap device is linkdown
> -----Original Message-----
> From: Avi Cohen (A)
> Sent: Monday, 19 June, 2017 3:09 PM
> To: 'ovs-discuss@openvswitch.org'; 'users@dpdk.org'
> Subject: RE: OVS-DPDK - af_packet vdev configuration - Error
>
> OK - solved
> The problem was with the device MTU which is set in the af_packet to 1518,
> In my port creation I set its MTU to 9000 I've changed the MTU in the
> af_packet driver to 9000
>
> > -----Original Message-----
> > From: Avi Cohen (A)
> > Sent: Sunday, 18 June, 2017 5:45 PM
> > To: 'ovs-discuss@openvswitch.org'; 'users@dpdk.org'
> > Subject: RE: OVS-DPDK - af_packet vdev configuration - Error
> >
> > I made upgrade to ovs2.7.0 and dpdk17.02.1 And got these error
> > msgs when I run
> > ovs-vsctl add-port br0 tap1 -- set Interface tap1 type=dpdk \
> > options:dpdk-devargs=eth_af_packet0,iface=tap1
> >
> > Jun 18 14:36:29 ip-172-31-100-80 ovs-vswitchd[54914]:
> > ovs|00047|netdev_dpdk|INFO|Device 'eth_af_packet0,iface=tap1'
> attached
> > to DPDK
> >
> > Jun 18 14:36:29 ip-172-31-100-80 ovs-vswitchd[54914]:
> > ovs|00050|netdev_dpdk|WARN|Interface tap1 eth_dev setup error Invalid
> > argument
> >
> > Jun 18 14:36:29 ip-172-31-100-80 ovs-vswitchd[54914]:
> > ovs|00051|netdev_dpdk|ERR|Interface tap1(rxq:1 txq:1) configure error:
> > Invalid argument
> >
> > Jun 18 14:36:29 ip-172-31-100-80 ovs-vswitchd[54914]:
> > ovs|00052|dpif_netdev|ERR|Failed to set interface tap1 new
> > ovs|00052|configuration
> >
> > Jun 18 14:36:29 ip-172-31-100-80 ovs-vswitchd[54914]:
> > ovs|00053|bridge|WARN|could not add network device tap1 to ofproto
> (No
> > such device)
> >
> > Can someone tell what is wrong with my cli command ?
> > Best Regards
> > avi
> >
> > > -----Original Message-----
> > > From: Avi Cohen (A)
> > > Sent: Sunday, 18 June, 2017 1:59 PM
> > > To: ovs-discuss@openvswitch.org; users@dpdk.org
> > > Subject: OVS-DPDK - af_packet vdev configuration - Error
> > >
> > > Hi All,
> > >
> > > I have ovs 2.6.1 with dpdk-stable-16.07.2 , I'm trying to create
> > > an af_packet vdev interface with the following commands:
> > >
> > > 1. ip tuntap add dev tap1 mode tap
> > >
> > > 2. ovs-vsctl add-port br0 tap1 -- set Interface tap1 type=dpdk \
> > > options:dpdk-devargs=eth_af_packet0,iface=tap1
> > >
> > > but I get an error message [could not open network device tap1 - No
> > > such device ]
> > >
> > > can you assist how to set this interface ?
> > >
> > > Best Regards
> > > avi
next reply other threads:[~2017-06-19 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 13:59 Avi Cohen (A) [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-19 12:08 Avi Cohen (A)
2017-06-18 14:44 Avi Cohen (A)
2017-06-18 10:58 Avi Cohen (A)
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=B84047ECBD981D4B93EAE5A6245AA361013C1F82@FRAEML521-MBX.china.huawei.com \
--to=avi.cohen@huawei.com \
--cc=ovs-discuss@openvswitch.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).