You should probably ask DPDK questions on a DPDK mailing list.

On Fri, Jan 08, 2016 at 07:51:24PM +0000, Sundar Ramakrishnan wrote:
> Thanks Ben for your input. I worked upon building dpdk 2.1 and this is what I 
> got - 
> 
>   CC [M]  
> /home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_hwmon.o
>   CC [M]  
> /home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.o/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:
>  In function 
> ‘igb_ndo_bridge_getlink’:/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:2284:2:
>  error: too few arguments to function ‘ndo_dflt_bridge_getlink’  return 
> ndo_dflt_bridge_getlink(skb, pid, seq, dev, mode);  ^In file included from 
> /usr/src/kernels/3.10.0-327.4.4.el7.x86_64/include/net/dst.h:13:0,            
>      from /usr/src/kernels/3.10.0-327.4.4.el7.x86_64/include/net/sock.h:68,   
>               from 
> /usr/src/kernels/3.10.0-327.4.4.el7.x86_64/include/linux/tcp.h:23,            
>      from 
> /home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:34:/usr/src/kernels/3.10.0-327.4.4.el7.x86_64/include/linux/rtnetlink.h:87:12:
>  note: declared here extern int ndo_dflt_bridge_getlink(struct sk_buff *skb, 
> u32 pid, u32 seq,            
> ^/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:
>  In function 
> ‘igb_xmit_frame_ring’:/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:5498:2:
>  error: implicit declaration of function ‘vlan_tx_tag_present’ 
> [-Werror=implicit-function-declaration]  if (vlan_tx_tag_present(skb)) {  
> ^/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:5500:3:
>  error: implicit declaration of function ‘vlan_tx_tag_ge ’ 
> [-Werror=implicit-function-declaration]   tx_flags |= (vlan_tx_tag_get(skb) 
> << IGB_TX_FLAGS_VLAN_SHIFT);   
> ^/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:
>  In function 
> ‘igb_ndo_get_vf_config’:/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:9467:5:
>  error: ‘struct ifla_vf_info’ has no member named ‘tx_rate’  ivi->tx_rate = 
> adapter->vf_data[vf].tx_rate;     
> ^/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:
>  In function 
> ‘igb_ndo_bridge_getlink’:/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.c:2286:1:
>  error: control reaches end of non-void function [-Werror=return-type] } 
> ^cc1: all warnings being treated as errorsmake[10]: *** 
> [/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/igb_main.o]
>  Error 1make[9]: *** 
> [_module_/home/dpdk-2.1.0/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni]
>  Error 2make[8]: *** [sub-make] Error 2make[7]: *** [rte_kni.ko] Error 
> 2make[6]: *** [kni] Error 2make[5]: *** [linuxapp] Error 2make[4]: *** 
> [librte_eal] Error 2make[3]: *** [lib] Error 2make[2]: *** [all] Error 
> 2make[1]: *** [x86_64-native-linuxapp-gcc_install] Error 2make: *** [install] 
> Error 2
> 
> 
>     On Friday, January 8, 2016 2:31 PM, "[email protected]" 
> <[email protected]> wrote:
>  
> 
>  Send discuss mailing list submissions to
>     [email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>     http://openvswitch.org/mailman/listinfo/discuss
> or, via email, send a message with subject or body 'help' to
>     [email protected]
> 
> You can reach the person managing the list at
>     [email protected]
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of discuss digest..."
> 
> 
> Today's Topics:
> 
>   1. Openvswitch Compatibility With DPDK on CentOS 7
>       (Sundar Ramakrishnan)
>   2. Re: systemd ovs-vswitchd starts too early
>       (=?UTF-8?Q?Beno=c3=aet?=)
>   3. Re: Openvswitch Compatibility With DPDK on CentOS 7 (Ben Pfaff)
>   4. Re: systemd ovs-vswitchd starts too early (Guru Shetty)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 8 Jan 2016 17:02:44 +0000 (UTC)
> From: Sundar Ramakrishnan <[email protected]>
> To: "[email protected]" <[email protected]>
> Subject: [ovs-discuss] Openvswitch Compatibility With DPDK on CentOS 7
> Message-ID:
>     <[email protected]>
> Content-Type: text/plain; charset="utf-8"
> 
> Hello,
> I am trying to install openvswitch 2.4.0 with dpdk 2.2.0 but I seem to hit 
> the same issue in spite of following several documentation guides available 
> on Openvswitch/Intel/DPDK etc.,
> Error snapshot upon running ./configure 
> --with-dpdk=/usr/src/dpdk-2.2.0/x86_64-native-linuxapp-gcc
> checking whether gcc -std=gnu99 accepts -Wno-unused-parameter... yeschecking 
> target hint for cgcc... x86_64checking whether make has GNU make $(if) 
> extension... yesconfigure: error: cannot link with dpdk
> I seek your expert opinion on the following - 
> 1. Openvswitch is supported on RHEL/CentOS 7 and up?
> 2. DPDK based Openvswitch is also supported on RHEL/CentOS 7?
> 3. Anyone who has tried this and has documentation?
> Please help with some guidance.
> Thanks-sundar
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://openvswitch.org/pipermail/discuss/attachments/20160108/6a3a72da/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 8 Jan 2016 19:36:55 +0100
> From: "=?UTF-8?Q?Beno=c3=aet?=" <[email protected]>
> To: [email protected]
> Subject: Re: [ovs-discuss] systemd ovs-vswitchd starts too early
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
> 
> Thanks Ian
> 
> I tried to change Before = network.target to After = network.target but 
> same issue..
> what do you think it would bring to add this oneshot service as I see it 
> only launch the openvswitch-nonetwork.service?
> 
> 
> On 01/08/16 16:51, Ian Pilcher wrote:
> > On 01/08/2016 09:27 AM, Benoît wrote:
> >> it is using /etc/systemd/network
> >> and to start ovs :
> >> /etc/systemd/system/multi-user.target.wants/ovs-vswitchd.service
> >> [Unit]
> >> Description    = Open vSwitch Daemon
> >> Documentation  = man:ovs-vswitchd
> >> Wants          = network.target
> >> Before        = network.target
> >> Requires      = ovsdb-server.service
> >> After          = ovsdb-server.service
> >>
> >> [Service]
> >> ExecStartPre = /sbin/modprobe openvswitch
> >> PIDFile = /run/openvswitch/ovs-vswitchd.pid
> >> ExecStart = /usr/sbin/ovs-vswitchd
> >> --pidfile=/run/openvswitch/ovs-vswitchd.pid
> >
> > It looks like Arch hasn't split the Open vSwitch service into pre- and
> > post-network stages.  Here's what Fedora does:
> >
> > $ cat openvswitch.service
> > [Unit]
> > Description=Open vSwitch
> > After=syslog.target network.target openvswitch-nonetwork.service
> > Requires=openvswitch-nonetwork.service
> >
> > [Service]
> > Type=oneshot
> > ExecStart=/bin/true
> > ExecStop=/bin/true
> > RemainAfterExit=yes
> >
> > [Install]
> > WantedBy=multi-user.target
> >
> >
> > $ cat openvswitch-nonetwork.service
> > [Unit]
> > Description=Open vSwitch Internal Unit
> > After=syslog.target
> > PartOf=openvswitch.service
> > Wants=openvswitch.service
> >
> > [Service]
> > Type=oneshot
> > RemainAfterExit=yes
> > EnvironmentFile=-/etc/sysconfig/openvswitch
> > ExecStart=/usr/share/openvswitch/scripts/ovs-ctl start \
> >          --system-id=random $OPTIONS
> > ExecStop=/usr/share/openvswitch/scripts/ovs-ctl stop
> > RuntimeDirectory=openvswitch
> > RuntimeDirectoryMode=0755
> >
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://openvswitch.org/pipermail/discuss/attachments/20160108/c426fb6d/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 3
> Date: Fri, 8 Jan 2016 11:11:24 -0800
> From: Ben Pfaff <[email protected]>
> To: Sundar Ramakrishnan <[email protected]>
> Cc: "[email protected]" <[email protected]>
> Subject: Re: [ovs-discuss] Openvswitch Compatibility With DPDK on
>     CentOS 7
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
> 
> On Fri, Jan 08, 2016 at 05:02:44PM +0000, Sundar Ramakrishnan wrote:
> > I am trying to install openvswitch 2.4.0 with dpdk 2.2.0 but I seem to
> > hit the same issue in spite of following several documentation guides
> > available on Openvswitch/Intel/DPDK etc.,
> 
> INSTALL.DPDK.md says that OVS requires DPDK 2.1.
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Fri, 8 Jan 2016 11:31:12 -0800
> From: Guru Shetty <[email protected]>
> To: [email protected]
> Cc: discuss <[email protected]>
> Subject: Re: [ovs-discuss] systemd ovs-vswitchd starts too early
> Message-ID:
>     <CAM_3v9Kj99vXyxnJx2f17om-=ei9fc0cSwCpLAyM=ocaryo...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> >
> >
> > what do you think it would bring to add this oneshot service as I see it
> > only launch the openvswitch-nonetwork.service?
> >
> 
> If I remember correctly, fedora split this for the following reasons.
> 
>  openvswitch service will start after network. But network will look at
> ifcfg-* scripts. If one of those scripts has openvswitch device to be
> configured, it can't start it because openvswitch is not yet started.
> 
> So Fedora, added the following:
> https://github.com/openvswitch/ovs/blob/master/rhel/etc_sysconfig_network-scripts_ifup-ovs#L63
> 
> What the above does is that it will force start
> openvswitch-nonetwork.service even before openvswitch.service starts.
> 
> 
> 
> 
> >
> >
> > On 01/08/16 16:51, Ian Pilcher wrote:
> >
> > On 01/08/2016 09:27 AM, Benoît wrote:
> >
> > it is using /etc/systemd/network
> > and to start ovs :
> > /etc/systemd/system/multi-user.target.wants/ovs-vswitchd.service
> > [Unit]
> > Description    = Open vSwitch Daemon
> > Documentation  = man:ovs-vswitchd
> > Wants          = network.target
> > Before        = network.target
> > Requires      = ovsdb-server.service
> > After          = ovsdb-server.service
> >
> > [Service]
> > ExecStartPre = /sbin/modprobe openvswitch
> > PIDFile = /run/openvswitch/ovs-vswitchd.pid
> > ExecStart = /usr/sbin/ovs-vswitchd
> > --pidfile=/run/openvswitch/ovs-vswitchd.pid
> >
> >
> > It looks like Arch hasn't split the Open vSwitch service into pre- and
> > post-network stages.  Here's what Fedora does:
> >
> > $ cat openvswitch.service
> > [Unit]
> > Description=Open vSwitch
> > After=syslog.target network.target openvswitch-nonetwork.service
> > Requires=openvswitch-nonetwork.service
> >
> > [Service]
> > Type=oneshot
> > ExecStart=/bin/true
> > ExecStop=/bin/true
> > RemainAfterExit=yes
> >
> > [Install]
> > WantedBy=multi-user.target
> >
> >
> > $ cat openvswitch-nonetwork.service
> > [Unit]
> > Description=Open vSwitch Internal Unit
> > After=syslog.target
> > PartOf=openvswitch.service
> > Wants=openvswitch.service
> >
> > [Service]
> > Type=oneshot
> > RemainAfterExit=yes
> > EnvironmentFile=-/etc/sysconfig/openvswitch
> > ExecStart=/usr/share/openvswitch/scripts/ovs-ctl start \
> >          --system-id=random $OPTIONS
> > ExecStop=/usr/share/openvswitch/scripts/ovs-ctl stop
> > RuntimeDirectory=openvswitch
> > RuntimeDirectoryMode=0755
> >
> >
> >
> > _______________________________________________
> > discuss mailing list
> > [email protected]
> > http://openvswitch.org/mailman/listinfo/discuss
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://openvswitch.org/pipermail/discuss/attachments/20160108/65aa4dea/attachment.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> discuss mailing list
> [email protected]
> http://openvswitch.org/mailman/listinfo/discuss
> 
> 
> ------------------------------
> 
> End of discuss Digest, Vol 79, Issue 27
> ***************************************
> 
> 
>   

> _______________________________________________
> discuss mailing list
> [email protected]
> http://openvswitch.org/mailman/listinfo/discuss

_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to