[dpdk-dev] Question about ip fragment library

[William Rolinson]

Hi,all:

Recently, I am reading source code about ipv4 fragment in DPDK 1.7.0.
I am confused about ip packet with options. it seems that DPDK ip frag lib 
would omit all options from all fragments except the first one. However, in my 
opinion, some options must be present in all fragments, others options can be 
omitted from all but the first fragment. Is it a bug or not? I am afraid I 
don?t know much about that.   I need help. Thank you very much.

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

[Zhan, Zhaochen]

Tested by Zhan, Zhaochen 
Applying these patches on the dpdk-1.7.0, we verified the compilation on 
FreeBSD10.0 with Clang 3.3 and Fedora20 with Clang 3.4.
We also verified some simple test case (pmd, cmdline, hello_world and timer) on 
FreeBSD with Clang 3.3.


> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Bruce Richardson
> Sent: Tuesday, July 08, 2014 7:37 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH 0/6] Clang compilation support on FreeBSD and
> Linux
> 
> 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 with clang v3.3 on FreeBSD 10 and clang v3.4 on
> Fedora linux 20. The example apps folder has not been tested at this time,
> this
> patch set only focuses on the core libraries and apps.
> 
> Bruce Richardson (6):
>   pmd_bond: add missing variable initialization
>   Makefiles: add clang to compiler if/else block
>   mk: Ensure correct detection of SSE4.2 on FreeBSD
>   acl: add nmmintrin.h header to allow clang compilation
>   mk: add toolchain for clang and linuxapp target
>   config: add compile target for clang on BSD
> 
>  config/defconfig_x86_64-native-bsdapp-clang   | 71
> 
>  config/defconfig_x86_64-native-linuxapp-clang | 63
> ++
>  lib/librte_acl/acl_bld.c  |  1 +
>  lib/librte_pmd_bond/rte_eth_bond_pmd.c|  2 +-
>  lib/librte_pmd_i40e/Makefile  |  9 
>  lib/librte_pmd_ixgbe/Makefile |  7 +++
>  lib/librte_pmd_vmxnet3/Makefile   |  7 +++
>  mk/machine/native/rte.vars.mk | 12 +
>  mk/toolchain/clang/rte.toolchain-compat.mk| 43 +++
>  mk/toolchain/clang/rte.vars.mk| 77
> +++
>  10 files changed, 291 insertions(+), 1 deletion(-)
>  create mode 100644 config/defconfig_x86_64-native-bsdapp-clang
>  create mode 100644 config/defconfig_x86_64-native-linuxapp-clang
>  create mode 100644 mk/toolchain/clang/rte.toolchain-compat.mk
>  create mode 100644 mk/toolchain/clang/rte.vars.mk
> 
> --
> 1.9.3

[dpdk-dev] DPDK Performance issue with l2fwd

[zachary....@cas-well.com]

Hey Guys,

Recently, I have used l2fwd to test 160G (82599 10G * 16 ports), but I
got a strange pheromone in my test.

When I used 12 ports to test the performance of l2fwd, it can work fine
and achieve 120G.
But it got abnormal when I using over than 12 port. Part of ports seems
something wrong and no any Tx/Rx.
Has anyone know about this?

My testing Environment.
1. E5-2658 v2 (10 cores) * 2
http://ark.intel.com/zh-tw/products/76160/Intel-Xeon-Processor-E5-2658-v2-25M-Cache-2_40-GHz
2. one core handle one port. (In order to get best performance.)
3. No any QPI crossing  issue.
4. l2fwd parameters
 4.1 -c 0xF0FF -- -P 0xF00FF  => 120G get!
 4.2 -c 0xFF0FF -- -P 0xFF0FF => Failed! Only first 10 ports can
work well.
 4.3 -c 0x3F3FF -- -P 0x3F3FF => Failed! Only first 10 ports can
work well.

BTW, I have tried lots of parameter sets and if I set the ports number
over than 12 ports, it only first 10 ports got work.
Else, everything got well.

Can anyone help me to solve the issue? Or DPDK only can set less equal
than 12 ports?
Or DPDK max throughput is 120G?

? This email may contain 
confidential information. Please do not use or disclose it in any way and 
delete it if you are not the intended recipient.

[dpdk-dev] DPDK Performance issue with l2fwd

[Alex Markuze]

Hi Zachary,
Your issue may be with the PCI-e 3, with 16 lanes Each slot is limited to
128Gb/s[3].
Now, AFAIK[1] the CPU is connected to the  I/O with a single PCI-E slot.

Several thoughts that may help you:

1. You can figure out the max b/w by running netsurf over the kernel
interfaces (w/o DPDK). Each CPU can handle the Netperf and the Completion
interrupts with grace (packets of 64K and all offloads on) for 10Gb nics.
With more then 10 Nics I would disable the IRQ balancer and make sure
interrupts are spread evenly by setting the  IRQ affinity manually [2].
As long as you have a physical core(NO hyperthreading) per NIC port you can
figure out the MAX B/W you can get with all the nics.

2. You can try using (If available to you , obviously) 40Gb and 56Gb Nics
(Mellanox), In this case for each Netperf flow you will need to separate
each Netperf Stream and the interrupts to different Cores to Reach wire
speed as long as both cores are on the same NUMA node(lscpu).

Hope this helps.

[1]
http://komposter.com.ua/documents/PCI_Express_Base_Specification_Revision_3.0.pdf
[2]
http://h50146.www5.hp.com/products/software/oe/linux/mainstream/support/whitepaper/pdfs/4AA4-9294ENW.pdf
[3]http://en.wikipedia.org/wiki/PCI_Express#PCI_Express_3.x


On Thu, Jul 10, 2014 at 11:07 AM,  wrote:

> Hey Guys,
>
> Recently, I have used l2fwd to test 160G (82599 10G * 16 ports), but I
> got a strange pheromone in my test.
>
> When I used 12 ports to test the performance of l2fwd, it can work fine
> and achieve 120G.
> But it got abnormal when I using over than 12 port. Part of ports seems
> something wrong and no any Tx/Rx.
> Has anyone know about this?
>
> My testing Environment.
> 1. E5-2658 v2 (10 cores) * 2
>
> http://ark.intel.com/zh-tw/products/76160/Intel-Xeon-Processor-E5-2658-v2-25M-Cache-2_40-GHz
> 2. one core handle one port. (In order to get best performance.)
> 3. No any QPI crossing  issue.
> 4. l2fwd parameters
>  4.1 -c 0xF0FF -- -P 0xF00FF  => 120G get!
>  4.2 -c 0xFF0FF -- -P 0xFF0FF => Failed! Only first 10 ports can
> work well.
>  4.3 -c 0x3F3FF -- -P 0x3F3FF => Failed! Only first 10 ports can
> work well.
>
> BTW, I have tried lots of parameter sets and if I set the ports number
> over than 12 ports, it only first 10 ports got work.
> Else, everything got well.
>
> Can anyone help me to solve the issue? Or DPDK only can set less equal
> than 12 ports?
> Or DPDK max throughput is 120G?
>
> ? This email may contain
> confidential information. Please do not use or disclose it in any way and
> delete it if you are not the intended recipient.
>

[dpdk-dev] DPDK Performance issue with l2fwd

[zachary....@cas-well.com]

Hi Alex:

Thanks for your help.

I forget to describe some criteria in my original post.

At first, I has confirmed my 82599 has connected by PCIe Gen3 (Gen3 x8) speed. 
The theoretical bandwidth can support over 160G in total.
Hence, It should get full speed in my test.

Second, I have ever check the performance w/o DPDK in packet size 1518 in the 
same environment, and indeed it can get 160G totally (by IRQ balance method).
So, I was so surprised to get this kinds of result in DPDK (I also use size 
1518 to test DPDK).

BTW, I can get 120G throughput in 12 ports already. But when I add more than 12 
ports, I only can get 100G.
Why the performance gets less than 120G? Why only 10 ports works fine and NO Tx 
and Rx in the others?
Is it bugs or limitations in DPDK?

Has anyone every do the similar or the same test?


On 07/10/2014 04:40 PM, Alex Markuze wrote:
Hi Zachary,
Your issue may be with the PCI-e 3, with 16 lanes Each slot is limited to 
128Gb/s[3].
Now, AFAIK[1] the CPU is connected to the  I/O with a single PCI-E slot.

Several thoughts that may help you:

1. You can figure out the max b/w by running netsurf over the kernel interfaces 
(w/o DPDK). Each CPU can handle the Netperf and the Completion interrupts with 
grace (packets of 64K and all offloads on) for 10Gb nics.
With more then 10 Nics I would disable the IRQ balancer and make sure 
interrupts are spread evenly by setting the  IRQ affinity manually [2].
As long as you have a physical core(NO hyperthreading) per NIC port you can 
figure out the MAX B/W you can get with all the nics.

2. You can try using (If available to you , obviously) 40Gb and 56Gb Nics 
(Mellanox), In this case for each Netperf flow you will need to separate each 
Netperf Stream and the interrupts to different Cores to Reach wire speed as 
long as both cores are on the same NUMA node(lscpu).

Hope this helps.

[1]http://komposter.com.ua/documents/PCI_Express_Base_Specification_Revision_3.0.pdf
[2]http://h50146.www5.hp.com/products/software/oe/linux/mainstream/support/whitepaper/pdfs/4AA4-9294ENW.pdf
[3]http://en.wikipedia.org/wiki/PCI_Express#PCI_Express_3.x


On Thu, Jul 10, 2014 at 11:07 AM, mailto:Zachary.Jen at cas-well.com>> wrote:
Hey Guys,

Recently, I have used l2fwd to test 160G (82599 10G * 16 ports), but I
got a strange pheromone in my test.

When I used 12 ports to test the performance of l2fwd, it can work fine
and achieve 120G.
But it got abnormal when I using over than 12 port. Part of ports seems
something wrong and no any Tx/Rx.
Has anyone know about this?

My testing Environment.
1. E5-2658 v2 (10 cores) * 2
http://ark.intel.com/zh-tw/products/76160/Intel-Xeon-Processor-E5-2658-v2-25M-Cache-2_40-GHz
2. one core handle one port. (In order to get best performance.)
3. No any QPI crossing  issue.
4. l2fwd parameters
 4.1 -c 0xF0FF -- -P 0xF00FF  => 120G get!
 4.2 -c 0xFF0FF -- -P 0xFF0FF => Failed! Only first 10 ports can
work well.
 4.3 -c 0x3F3FF -- -P 0x3F3FF => Failed! Only first 10 ports can
work well.

BTW, I have tried lots of parameter sets and if I set the ports number
over than 12 ports, it only first 10 ports got work.
Else, everything got well.

Can anyone help me to solve the issue? Or DPDK only can set less equal
than 12 ports?
Or DPDK max throughput is 120G?

? This email may contain 
confidential information. Please do not use or disclose it in any way and 
delete it if you are not the intended recipient.



--
Best Regards,
Zachary Jen

Software RD
CAS-WELL Inc.
8th Floor, No. 242, Bo-Ai St., Shu-Lin City, Taipei County 238, Taiwan
Tel: +886-2-7705-#6305
Fax: +886-2-7731-9988

? This email may contain 
confidential information. Please do not use or disclose it in any way and 
delete it if you are not the intended recipient.

[dpdk-dev] testpmd unable to set allmulti for VF

[Tomasz K]

Hi All

I have an Intel 82599 with VFs created using Kernel Driver.
Two of the VFs are bound to DPDK Driver.

I'm trying to enable multicast for both VFs with testpmd app but it doesn't
work.
Output below:
testpmd> show port info 0

* Infos for port 0  *
MAC address: 02:09:C0:5C:65:18
Connect to socket: 0
memory allocation on the socket: 0
Link status: up
Link speed: 100 Mbps
Link duplex: half-duplex
Promiscuous mode: disabled
Allmulticast mode: disabled
Maximum number of MAC addresses: 128
Maximum number of MAC addresses of hash filtering: 4096
VLAN offload:
  strip on
  filter on
  qinq(extend) off
testpmd>
testpmd>
testpmd>
testpmd> set allmulti 0 on
testpmd>
testpmd>
testpmd> show port info 0

* Infos for port 0  *
MAC address: 02:09:C0:5C:65:18
Connect to socket: 0
memory allocation on the socket: 0
Link status: up
Link speed: 100 Mbps
Link duplex: half-duplex
Promiscuous mode: disabled
Allmulticast mode: disabled
Maximum number of MAC addresses: 128
Maximum number of MAC addresses of hash filtering: 4096
VLAN offload:
  strip on
  filter on
  qinq(extend) off
testpmd>

I also tried to bind VFs to VFIO driver but this also doesn't work.

So my question is: is it possible to set multicast for VF. If yes then why
testpmd is unable to set it

Setup:
HP Dl380p, Ubuntu 14, Intel 82599

Thanks
Tomasz

[dpdk-dev] DPDK Performance issue with l2fwd

[Richardson, Bruce]

Hi,

Have you tried running a test with 16 ports using any other applications, for 
example testpmd?

Regards,
/Bruce

> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Zachary.Jen at cas-
> well.com
> Sent: Thursday, July 10, 2014 2:29 AM
> To: dev at dpdk.org
> Cc: Alan.Yu at cas-well.com
> Subject: Re: [dpdk-dev] DPDK Performance issue with l2fwd
> 
> Hi Alex:
> 
> Thanks for your help.
> 
> I forget to describe some criteria in my original post.
> 
> At first, I has confirmed my 82599 has connected by PCIe Gen3 (Gen3 x8) speed.
> The theoretical bandwidth can support over 160G in total.
> Hence, It should get full speed in my test.
> 
> Second, I have ever check the performance w/o DPDK in packet size 1518 in the
> same environment, and indeed it can get 160G totally (by IRQ balance method).
> So, I was so surprised to get this kinds of result in DPDK (I also use size 
> 1518 to
> test DPDK).
> 
> BTW, I can get 120G throughput in 12 ports already. But when I add more than
> 12 ports, I only can get 100G.
> Why the performance gets less than 120G? Why only 10 ports works fine and NO
> Tx and Rx in the others?
> Is it bugs or limitations in DPDK?
> 
> Has anyone every do the similar or the same test?
> 
> 
> On 07/10/2014 04:40 PM, Alex Markuze wrote:
> Hi Zachary,
> Your issue may be with the PCI-e 3, with 16 lanes Each slot is limited to
> 128Gb/s[3].
> Now, AFAIK[1] the CPU is connected to the  I/O with a single PCI-E slot.
> 
> Several thoughts that may help you:
> 
> 1. You can figure out the max b/w by running netsurf over the kernel 
> interfaces
> (w/o DPDK). Each CPU can handle the Netperf and the Completion interrupts
> with grace (packets of 64K and all offloads on) for 10Gb nics.
> With more then 10 Nics I would disable the IRQ balancer and make sure
> interrupts are spread evenly by setting the  IRQ affinity manually [2].
> As long as you have a physical core(NO hyperthreading) per NIC port you can
> figure out the MAX B/W you can get with all the nics.
> 
> 2. You can try using (If available to you , obviously) 40Gb and 56Gb Nics
> (Mellanox), In this case for each Netperf flow you will need to separate each
> Netperf Stream and the interrupts to different Cores to Reach wire speed as
> long as both cores are on the same NUMA node(lscpu).
> 
> Hope this helps.
> 
> [1]http://komposter.com.ua/documents/PCI_Express_Base_Specification_Revis
> ion_3.0.pdf
> [2]http://h50146.www5.hp.com/products/software/oe/linux/mainstream/supp
> ort/whitepaper/pdfs/4AA4-9294ENW.pdf
> [3]http://en.wikipedia.org/wiki/PCI_Express#PCI_Express_3.x
> 
> 
> On Thu, Jul 10, 2014 at 11:07 AM,  well.com> wrote:
> Hey Guys,
> 
> Recently, I have used l2fwd to test 160G (82599 10G * 16 ports), but I
> got a strange pheromone in my test.
> 
> When I used 12 ports to test the performance of l2fwd, it can work fine
> and achieve 120G.
> But it got abnormal when I using over than 12 port. Part of ports seems
> something wrong and no any Tx/Rx.
> Has anyone know about this?
> 
> My testing Environment.
> 1. E5-2658 v2 (10 cores) * 2
> http://ark.intel.com/zh-tw/products/76160/Intel-Xeon-Processor-E5-2658-v2-
> 25M-Cache-2_40-GHz
> 2. one core handle one port. (In order to get best performance.)
> 3. No any QPI crossing  issue.
> 4. l2fwd parameters
>  4.1 -c 0xF0FF -- -P 0xF00FF  => 120G get!
>  4.2 -c 0xFF0FF -- -P 0xFF0FF => Failed! Only first 10 ports can
> work well.
>  4.3 -c 0x3F3FF -- -P 0x3F3FF => Failed! Only first 10 ports can
> work well.
> 
> BTW, I have tried lots of parameter sets and if I set the ports number
> over than 12 ports, it only first 10 ports got work.
> Else, everything got well.
> 
> Can anyone help me to solve the issue? Or DPDK only can set less equal
> than 12 ports?
> Or DPDK max throughput is 120G?
> 
> 
> ? This email may contain confidential
> information. Please do not use or disclose it in any way and delete it if you 
> are
> not the intended recipient.
> 
> 
> 
> --
> Best Regards,
> Zachary Jen
> 
> Software RD
> CAS-WELL Inc.
> 8th Floor, No. 242, Bo-Ai St., Shu-Lin City, Taipei County 238, Taiwan
> Tel: +886-2-7705-#6305
> Fax: +886-2-7731-9988
> 
> 
> ? This email may contain confidential
> information. Please do not use or disclose it in any way and delete it if you 
> are
> not the intended recipient.

[dpdk-dev] [PATCH] librte_pmd_packet: add PMD for AF_PACKET-based virtual devices

[John W. Linville]

This is a Linux-specific virtual PMD driver backed by an AF_PACKET
socket.  This implementation uses mmap'ed ring buffers to limit copying
and user/kernel transitions.  The PACKET_FANOUT_HASH behavior of
AF_PACKET is used for frame reception.  In the current implementation,
Tx and Rx queues are always paired, and therefore are always equal
in number -- changing this would be a Simple Matter Of Programming.

Interfaces of this type are created with a command line option like
"--vdev=eth_packet0,iface=...".  There are a number of options availabe
as arguments:

 - Interface is chosen by "iface" (required)
 - Number of queue pairs set by "qpairs" (optional, default: 16)
 - AF_PACKET MMAP block size set by "blocksz" (optional, default: 4096)
 - AF_PACKET MMAP frame size set by "framesz" (optional, default: 2048)
 - AF_PACKET MMAP frame count set by "framecnt" (optional, default: 512)

Signed-off-by: John W. Linville 
---
This PMD is intended to provide a means for using DPDK on a broad
range of hardware without hardware-specific PMDs and (hopefully)
with better performance than what PCAP offers in Linux.  This might
be useful as a development platform for DPDK applications when
DPDK-supported hardware is expensive or unavailable.

 config/common_bsdapp   |   5 +
 config/common_linuxapp |   5 +
 lib/Makefile   |   1 +
 lib/librte_eal/linuxapp/eal/Makefile   |   1 +
 lib/librte_pmd_packet/Makefile |  60 +++
 lib/librte_pmd_packet/rte_eth_packet.c | 826 +
 lib/librte_pmd_packet/rte_eth_packet.h |  55 +++
 mk/rte.app.mk  |   4 +
 8 files changed, 957 insertions(+)
 create mode 100644 lib/librte_pmd_packet/Makefile
 create mode 100644 lib/librte_pmd_packet/rte_eth_packet.c
 create mode 100644 lib/librte_pmd_packet/rte_eth_packet.h

diff --git a/config/common_bsdapp b/config/common_bsdapp
index 943dce8f1ede..c317f031278e 100644
--- a/config/common_bsdapp
+++ b/config/common_bsdapp
@@ -226,6 +226,11 @@ CONFIG_RTE_LIBRTE_PMD_PCAP=y
 CONFIG_RTE_LIBRTE_PMD_BOND=y

 #
+# Compile software PMD backed by AF_PACKET sockets (Linux only)
+#
+CONFIG_RTE_LIBRTE_PMD_PACKET=n
+
+#
 # Do prefetch of packet data within PMD driver receive function
 #
 CONFIG_RTE_PMD_PACKET_PREFETCH=y
diff --git a/config/common_linuxapp b/config/common_linuxapp
index 7bf5d80d4e26..f9e7bc3015ec 100644
--- a/config/common_linuxapp
+++ b/config/common_linuxapp
@@ -249,6 +249,11 @@ CONFIG_RTE_LIBRTE_PMD_PCAP=n
 CONFIG_RTE_LIBRTE_PMD_BOND=y

 #
+# Compile software PMD backed by AF_PACKET sockets (Linux only)
+#
+CONFIG_RTE_LIBRTE_PMD_PACKET=y
+
+#
 # Compile Xen PMD
 #
 CONFIG_RTE_LIBRTE_PMD_XENVIRT=n
diff --git a/lib/Makefile b/lib/Makefile
index 10c5bb3045bc..930fadf29898 100644
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -47,6 +47,7 @@ DIRS-$(CONFIG_RTE_LIBRTE_I40E_PMD) += librte_pmd_i40e
 DIRS-$(CONFIG_RTE_LIBRTE_PMD_BOND) += librte_pmd_bond
 DIRS-$(CONFIG_RTE_LIBRTE_PMD_RING) += librte_pmd_ring
 DIRS-$(CONFIG_RTE_LIBRTE_PMD_PCAP) += librte_pmd_pcap
+DIRS-$(CONFIG_RTE_LIBRTE_PMD_PACKET) += librte_pmd_packet
 DIRS-$(CONFIG_RTE_LIBRTE_VIRTIO_PMD) += librte_pmd_virtio
 DIRS-$(CONFIG_RTE_LIBRTE_VMXNET3_PMD) += librte_pmd_vmxnet3
 DIRS-$(CONFIG_RTE_LIBRTE_PMD_XENVIRT) += librte_pmd_xenvirt
diff --git a/lib/librte_eal/linuxapp/eal/Makefile 
b/lib/librte_eal/linuxapp/eal/Makefile
index 756d6b0c9301..feed24a63272 100644
--- a/lib/librte_eal/linuxapp/eal/Makefile
+++ b/lib/librte_eal/linuxapp/eal/Makefile
@@ -44,6 +44,7 @@ CFLAGS += -I$(RTE_SDK)/lib/librte_ether
 CFLAGS += -I$(RTE_SDK)/lib/librte_ivshmem
 CFLAGS += -I$(RTE_SDK)/lib/librte_pmd_ring
 CFLAGS += -I$(RTE_SDK)/lib/librte_pmd_pcap
+CFLAGS += -I$(RTE_SDK)/lib/librte_pmd_packet
 CFLAGS += -I$(RTE_SDK)/lib/librte_pmd_xenvirt
 CFLAGS += $(WERROR_FLAGS) -O3

diff --git a/lib/librte_pmd_packet/Makefile b/lib/librte_pmd_packet/Makefile
new file mode 100644
index ..e1266fb992cd
--- /dev/null
+++ b/lib/librte_pmd_packet/Makefile
@@ -0,0 +1,60 @@
+#   BSD LICENSE
+#
+#   Copyright(c) 2014 John W. Linville 
+#   Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
+#   Copyright(c) 2014 6WIND S.A.
+#   All rights reserved.
+#
+#   Redistribution and use in source and binary forms, with or without
+#   modification, are permitted provided that the following conditions
+#   are met:
+#
+# * Redistributions of source code must retain the above copyright
+#   notice, this list of conditions and the following disclaimer.
+# * Redistributions in binary form must reproduce the above copyright
+#   notice, this list of conditions and the following disclaimer in
+#   the documentation and/or other materials provided with the
+#   distribution.
+# * Neither the name of Intel Corporation nor the names of its
+#   contributors may be used to endorse or promote products derived
+#   from this software without specific prior written permission.
+#
+#   T

[dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko

[Daniel, Christopher]

All,

I have the following configuration on my machine

Linux localhost.localdomain 3.12.6 #4 SMP Fri Dec 27 14:26:57 EST 2013 x86_64 
x86_64 x86_64 GNU/Linux : Centos


1)  Downloaded the latest version of DPK ( 1.7);


2)  Executing the quick start instructions ( running gcc 4.7.x)



3)  Having an issue with



  # insmod build/kmod/igb_uio.ko

I am getting

insmod: error inserting './build/kmod/igb_uio.ko': -1 Unknown symbol in module

dmesg:
igb_uio: Unknown symbol __fentry__ (err 0)

Please let me know what I'm missing.

Thanks
Chris

[dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko

[Jeff Shaw]

On Thu, Jul 10, 2014 at 09:53:20PM +, Daniel, Christopher wrote:
> 3)  Having an issue with
>   # insmod build/kmod/igb_uio.ko
> 
> I am getting
> 
> insmod: error inserting './build/kmod/igb_uio.ko': -1 Unknown symbol in module
> 
> dmesg:
> igb_uio: Unknown symbol __fentry__ (err 0)
> 

Did you 'modprobe uio'?

[dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko

[Daniel, Christopher]

Yes I did modprobe uio. I can see it listed with lsmod.

[root at localhost dpdk-1.7.0]# lsmod
ModuleSize   Used by
uio10343 0
nfnetlink_queue   11564 0
nfnetlink_log9334   0
nfnetlink   57422 nfnetlink_queue,nfnetlink_log
bluetooth 3711100
rfkill  20113   1 bluetooth
nls_utf8  1389  1


-Original Message-
From: Jeff Shaw [mailto:jeffrey.b.s...@intel.com] 
Sent: Thursday, July 10, 2014 6:09 PM
To: Daniel, Christopher
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko

On Thu, Jul 10, 2014 at 09:53:20PM +, Daniel, Christopher wrote:
> 3)  Having an issue with
>   # insmod build/kmod/igb_uio.ko
> 
> I am getting
> 
> insmod: error inserting './build/kmod/igb_uio.ko': -1 Unknown symbol in module
> 
> dmesg:
> igb_uio: Unknown symbol __fentry__ (err 0)
> 

Did you 'modprobe uio'?

[dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko

[Chris Wright]

* Daniel, Christopher (Chris.Daniel at flukenetworks.com) wrote:
> All,
> 
> I have the following configuration on my machine
> 
> Linux localhost.localdomain 3.12.6 #4 SMP Fri Dec 27 14:26:57 EST 2013 x86_64 
> x86_64 x86_64 GNU/Linux : Centos
> 
> 
> 1)  Downloaded the latest version of DPK ( 1.7);
> 
> 
> 2)  Executing the quick start instructions ( running gcc 4.7.x)
> 
> 
> 
> 3)  Having an issue with
> 
> 
> 
>   # insmod build/kmod/igb_uio.ko
> 
> I am getting
> 
> insmod: error inserting './build/kmod/igb_uio.ko': -1 Unknown symbol in module
> 
> dmesg:
> igb_uio: Unknown symbol __fentry__ (err 0)

seems like you have built module w/ CONFIG_FTRACE and built kernel
w/out.  did you manually set RTE_KERNELDIR when you built (if so, is it
pointing to the right location?)

thanks,
-chris

[dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko

[Daniel, Christopher]

Actually I did not build the kernel. It is unmodified from the original centos 
download.
I also did not change any build parameters while building the module.
Used all the defaults from the download and executed the commands as in the 
quick start guide.
Is there something I can change and rebuild the dpk module ?
Thanks for your help

> On Jul 10, 2014, at 6:31 PM, "Chris Wright"  wrote:
> 
> * Daniel, Christopher (Chris.Daniel at flukenetworks.com) wrote:
>> All,
>> 
>> I have the following configuration on my machine
>> 
>> Linux localhost.localdomain 3.12.6 #4 SMP Fri Dec 27 14:26:57 EST 2013 
>> x86_64 x86_64 x86_64 GNU/Linux : Centos
>> 
>> 
>> 1)  Downloaded the latest version of DPK ( 1.7);
>> 
>> 
>> 2)  Executing the quick start instructions ( running gcc 4.7.x)
>> 
>> 
>> 
>> 3)  Having an issue with
>> 
>> 
>> 
>>  # insmod build/kmod/igb_uio.ko
>> 
>> I am getting
>> 
>> insmod: error inserting './build/kmod/igb_uio.ko': -1 Unknown symbol in 
>> module
>> 
>> dmesg:
>> igb_uio: Unknown symbol __fentry__ (err 0)
> 
> seems like you have built module w/ CONFIG_FTRACE and built kernel
> w/out.  did you manually set RTE_KERNELDIR when you built (if so, is it
> pointing to the right location?)
> 
> thanks,
> -chris

[dpdk-dev] Error while inserting module /build/kmod/igb_uio.ko

[Chris Wright]

* Daniel, Christopher (Chris.Daniel at flukenetworks.com) wrote:
> > On Jul 10, 2014, at 6:31 PM, "Chris Wright"  wrote:
> > * Daniel, Christopher (Chris.Daniel at flukenetworks.com) wrote:
> >> Linux localhost.localdomain 3.12.6 #4 SMP Fri Dec 27 14:26:57 EST 2013 
> >> x86_64 x86_64 x86_64 GNU/Linux : Centos

OK, I expected to see a suffix like 3.12.6.el...(why I assumed you built
your own kernel)

> >> 1)  Downloaded the latest version of DPK ( 1.7);
> >> 2)  Executing the quick start instructions ( running gcc 4.7.x)
> >> 3)  Having an issue with
> >>  # insmod build/kmod/igb_uio.ko
> >> I am getting
> >> insmod: error inserting './build/kmod/igb_uio.ko': -1 Unknown symbol in 
> >> module
> >> 
> >> dmesg:
> >> igb_uio: Unknown symbol __fentry__ (err 0)
> > 
> > seems like you have built module w/ CONFIG_FTRACE and built kernel
> > w/out.  did you manually set RTE_KERNELDIR when you built (if so, is it
> > pointing to the right location?)
> 
> Actually I did not build the kernel. It is unmodified from the original 
> centos download.
> I also did not change any build parameters while building the module.
> Used all the defaults from the download and executed the commands as in the 
> quick start guide.
> Is there something I can change and rebuild the dpk module ?

Hmm, you could verify a couple things:

$ uname -r
$ grep __fentry__ /proc/kallsyms
$ grep CONFIG_FTRACE /lib/modules/$(uname -r)/build/.config

thanks,
-chris

[dpdk-dev] DPDK with Ubuntu 14.04?

[Matt Laswell]

Hey Folks,

I know that official support hasn't moved past Ubuntu 12.04 LTS yet, but
does anybody have any practical experience running with 14.04 LTS?  My team
has run into one compilation error so far with 1.7, but other than that
things look OK at first blush.  I'd like to move my product to 14.04 for a
variety of reasons, but would hate to spend time chasing down subtle
incompatibilities.  I'm guessing we're not the first ones to try this...

Thanks.

--
Matt Laswell
infinite io