[dpdk-dev] [PATCH] port: fix doxygen

2014-07-19 Thread Thomas Monjalon
> fix doxygen for rte_port_out_op_flush. > > Signed-off-by: Yao Zhao Acked-by: Thomas Monjalon Applied for version 1.7.1 Thanks -- Thomas

[dpdk-dev] [PATCH] nic_uio: add device ids for i40e devices

2014-07-19 Thread Thomas Monjalon
> > The FreeBSD nic_uio driver was missing the #defines to include the device > > ids > > for devices using the i40e driver. This change adds in the missing defines. > > > > Signed-off-by: Bruce Richardson > > Acked-by: Helin Zhang Applied for version 1.7.1 Thanks -- Thomas

[dpdk-dev] [PATCH] makefile: Substituted deprecated default target in app Makefile

2014-07-19 Thread Thomas Monjalon
> L3fwd-acl and ip pipeline apps were using old > x86_64-default-linuxapp-gcc as their default target, > instead of x86_64-native-linuxapp-gcc > > Signed-off-by: Pablo de Lara Acked-by: Thomas Monjalon Applied for version 1.7.1 Thanks -- Thomas

[dpdk-dev] [PATCH 0/6] Clang compilation support on FreeBSD and Linux

2014-07-19 Thread Thomas Monjalon
2014-07-08 00:36, Bruce Richardson: > This patch set enables clang compilation on FreeBSD and Linux. It includes > patches to fix a number of compilation errors thrown up by clang, and then > adds in the appropriate toolchain makefiles and compile-time configurations. > > This set has been tested

[dpdk-dev] [PATCH v2] kni: use netif_rx instead of netif_receive_skb in which ocurr deallock on userpace contex

2014-07-19 Thread Thomas Monjalon
2014-07-17 15:24, Alex Markuze: > On Thu, Jul 17, 2014 at 3:02 PM, Thomas Monjalon > > 2014-07-11 23:37, Yao-Po Wang: > >> Per netif_receive_skb function description, it may only be called from > >> interrupt contex, but KNI is run on kthread that like as user-space > >> contex. It may occur deallo

[dpdk-dev] [PATCH] kni: allow setting KNI device MAC address

2014-07-19 Thread Thomas Monjalon
> > Added relevant callback function to change a KNI device's MAC address > > > > Signed-off-by: Padam Jeet Singh > > Reviewed-by: Helin Zhang Applied for version 1.7.1 Thanks -- Thomas

[dpdk-dev] KNI interface

2014-07-19 Thread Harish Patil
Hello dpdk-dev, Went thru? couple of documentation but not very clear to me. Does using KNI means handing over all the packets received/transmitted by the poll mode driver to the linux stack or can it be controlled for the control packets only ? What is the KNI use-case (besides ethtool) and what a

[dpdk-dev] [PATCH 00/10] igb_uio related patches

2014-07-19 Thread Thomas Monjalon
2014-07-18 09:14, Stephen Hemminger: > Update patches so all are now bisectable, and incorporate comments. > Also fix the checkpatch warnings that are fixable. I've isolated all MSI additions in the dedicated commit. Acked-by: Thomas Monjalon Applied for version 1.7.1 What are the news about y

[dpdk-dev] KNI interface

2014-07-19 Thread Zhou, Danny
KNI is mainly designed for exception path or control plane packets that need to be pushed to Linux TCP/IP packets in the kernel. You can push all the packets that DPDK PMD received in the user space via KNI to kernel, but majority of them will be dropped for two reasons: 1) skb allocation/free

[dpdk-dev] KNI interface

2014-07-19 Thread Harish Patil
>KNI is mainly designed for exception path or control plane packets that >need to be pushed >to Linux TCP/IP packets in the kernel. You can push all the packets that >DPDK PMD received >in the user space via KNI to kernel, but majority of them will be dropped >for two reasons: 1) skb >allocation/