[dpdk-dev] No "pci_unbind.py" in tools subdirectory

[BYEONG-GI KIM]

Thank you for the reply.

By the way, I got an error message while compiling Open vSwitch. Is it
essential to bind a port to igb_uio module in order to compile Open vSwitch
without error? I just wonder whether the errors attached below just
happened because I did not bind the port to the module or not...

make RTE_TARGET=x86_64-ivshmem-linuxapp-gcc
...
/home/stack/dpdk/dpdk-1.6.0r2/x86_64-ivshmem-linuxapp-gcc/lib/librte_eal.a(eal.o):
In function `rte_eal_init':
eal.c:(.text+0xedf): undefined reference to `dlopen'
eal.c:(.text+0xefe): undefined reference to `dlerror'
collect2: error: ld returned 1 exit status
make[2]: *** [utilities/ovs-controller] Error 1
make[2]: Leaving directory `/home/stack/dpdk-ovs/openvswitch'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/stack/dpdk-ovs/openvswitch'
make: *** [all] Error 2

Best regards

Byeong-Gi KIM


2014-07-14 17:10 GMT+09:00 De Lara Guarch, Pablo <
pablo.de.lara.guarch at intel.com>:

> > -Original Message-
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Aravind
> > Sent: Monday, July 14, 2014 8:52 AM
> > To: BYEONG-GI KIM
> > Cc: dev at dpdk.org; Dpdk-ovs at lists.01.org
> > Subject: Re: [dpdk-dev] No "pci_unbind.py" in tools subdirectory
> >
> > Hi,
> >
> > You should be using igb_uio_bind.py , have a look at the quick start
> guide
> > : http://dpdk.org/doc/quick-start
> >
>
> Actually, now it is called dpdk_nic_bind.py :)
>
> >
> >
> > On Mon, Jul 14, 2014 at 1:09 PM, BYEONG-GI KIM 
> > wrote:
> >
> > > Hello.
> > >
> > > I'm sorry for the repeated question.
> > >
> > > I finally compiled DPDK successfully (there was a problem in the source
> > > code what I downloaded), and I'm moving to compile dpdk-ovs.
> > >
> > > Before compiling it, I'm trying to binding a network port to igb_uio
> > > module. In the dpdk-getting-started-guide, "pci_unbind.py" utility
> script
> > > is used to provide a view of the current state of the network ports on
> the
> > > system, and to bind/unbind those ports from the different kernel
> modules.
> > >
> > > The script, however, was not there in tools directory; There were only
> > > "igb_uio_bind.py". Is it fine as it is, or do I miss something?
> > >
> > > I downloaded the DPDK source from http://dpdk.org/browse/dpdk/refs/,
> and
> > > the file was dpdk-1.6.0r2.zip. I compiled both
> x86-64-defaultlinuxapp-gcc
> > > and x86-64-ivshmem-linuxapp-gcc now.
> > >
> > > Thanks in advance.
> > >
> > > Best regards
> > >
> > > Byeong-Gi KIM
> > >
>
>

[dpdk-dev] No "pci_unbind.py" in tools subdirectory

[BYEONG-GI KIM]

Hello.

I'm sorry for the repeated question.

I finally compiled DPDK successfully (there was a problem in the source
code what I downloaded), and I'm moving to compile dpdk-ovs.

Before compiling it, I'm trying to binding a network port to igb_uio
module. In the dpdk-getting-started-guide, "pci_unbind.py" utility script
is used to provide a view of the current state of the network ports on the
system, and to bind/unbind those ports from the different kernel modules.

The script, however, was not there in tools directory; There were only
"igb_uio_bind.py". Is it fine as it is, or do I miss something?

I downloaded the DPDK source from http://dpdk.org/browse/dpdk/refs/, and
the file was dpdk-1.6.0r2.zip. I compiled both x86-64-defaultlinuxapp-gcc
and x86-64-ivshmem-linuxapp-gcc now.

Thanks in advance.

Best regards

Byeong-Gi KIM

[dpdk-dev] [PATCH v2] 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: 1)
 - 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.

New in v2:

-- fixup some style issues found by check patch
-- use if_index as part of fanout group ID
-- set default number of queue pairs to 1

 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
+#  

[dpdk-dev] [PATCH] virtio: Fix 32bit pmd for 64bit kernel

[Vijayakumar Muthuvel Manickam]

*virtio_net_hdr_mem* member within *virtqueue* structure stores a
physical address and is defined as void ptr. When 32bit pmd is used
with 64bit kernel this leads to truncation of 64bit physical address
and pkt i/o does not work.
Changed *virtio_net_hdr_mem* to *phys_addr_t* type and
removed the typecasts

Signed-off-by: Vijayakumar Muthuvel Manickam 
---
 lib/librte_pmd_virtio/virtio_ethdev.c |6 +++---
 lib/librte_pmd_virtio/virtqueue.h |4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/lib/librte_pmd_virtio/virtio_ethdev.c
b/lib/librte_pmd_virtio/virtio_ethdev.c
index d4730f9..764a769 100644
--- a/lib/librte_pmd_virtio/virtio_ethdev.c
+++ b/lib/librte_pmd_virtio/virtio_ethdev.c
@@ -331,7 +331,7 @@ int virtio_dev_queue_setup(struct rte_eth_dev *dev,
PMD_INIT_LOG(DEBUG, "vq->vq_ring_mem:  0x%"PRIx64"\n",
(uint64_t)mz->phys_addr);
PMD_INIT_LOG(DEBUG, "vq->vq_ring_virt_mem: 0x%"PRIx64"\n",
(uint64_t)mz->addr);
vq->virtio_net_hdr_mz  = NULL;
-   vq->virtio_net_hdr_mem = (void *)NULL;
+   vq->virtio_net_hdr_mem = 0;

if (queue_type == VTNET_TQ) {
/*
@@ -347,7 +347,7 @@ int virtio_dev_queue_setup(struct rte_eth_dev *dev,
return -ENOMEM;
}
vq->virtio_net_hdr_mem =
-   (void *)(uintptr_t)vq->virtio_net_hdr_mz->phys_addr;
+   vq->virtio_net_hdr_mz->phys_addr;
memset(vq->virtio_net_hdr_mz->addr, 0,
vq_size * sizeof(struct virtio_net_hdr));
} else if (queue_type == VTNET_CQ) {
@@ -361,7 +361,7 @@ int virtio_dev_queue_setup(struct rte_eth_dev *dev,
return -ENOMEM;
}
vq->virtio_net_hdr_mem =
-   (void *)(uintptr_t)vq->virtio_net_hdr_mz->phys_addr;
+   vq->virtio_net_hdr_mz->phys_addr;
memset(vq->virtio_net_hdr_mz->addr, 0, PAGE_SIZE);
}

diff --git a/lib/librte_pmd_virtio/virtqueue.h
b/lib/librte_pmd_virtio/virtqueue.h
index a63723d..8d1fc14 100644
--- a/lib/librte_pmd_virtio/virtqueue.h
+++ b/lib/librte_pmd_virtio/virtqueue.h
@@ -152,7 +152,7 @@ struct virtqueue {
 */
uint16_t vq_used_cons_idx;
uint16_t vq_avail_idx;
-   void *virtio_net_hdr_mem; /**< hdr for each xmit packet */
+   phys_addr_t virtio_net_hdr_mem; /**< hdr for each xmit packet */

struct vq_desc_extra {
void  *cookie;
@@ -354,7 +354,7 @@ virtqueue_enqueue_xmit(struct virtqueue *txvq, struct
rte_mbuf *cookie)
dxp->ndescs = needed;

start_dp = txvq->vq_ring.desc;
-   start_dp[idx].addr  = (uint64_t)(uintptr_t)txvq->virtio_net_hdr_mem
+ idx * sizeof(struct virtio_net_hdr);
+   start_dp[idx].addr  = txvq->virtio_net_hdr_mem + idx *
sizeof(struct virtio_net_hdr);
start_dp[idx].len   = sizeof(struct virtio_net_hdr);
start_dp[idx].flags = VRING_DESC_F_NEXT;
idx = start_dp[idx].next;
--
1.7.1

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

[John W. Linville]

On Sat, Jul 12, 2014 at 12:30:34AM +0200, Thomas Monjalon wrote:
> About the form of the patch, I have 2 comments:
> 
> 1) A doc explaining the design, the dependencies and how it can be used would 
> be a great help. Could you write it in rst format?

What is rst format?  Are there other examples in the repository?

> 2) checkpatch.pl returns these errors:
> 
> ERROR:SPACING: space required before the open parenthesis '('
> #468: FILE: lib/librte_pmd_packet/rte_eth_packet.c:250:
> +   if(sockfd != -1)
> 
> ERROR:SPACING: space required before the open parenthesis '('
> #471: FILE: lib/librte_pmd_packet/rte_eth_packet.c:253:
> +   if(sockfd != -1)
> 
> ERROR:SPACING: spaces required around that '=' (ctx:VxV)
> #712: FILE: lib/librte_pmd_packet/rte_eth_packet.c:494:
> +   ifr.ifr_name[ifnamelen]='\0';

OK.  FWIW, at least the first two are slightly changed from what was
copied from the PCAP driver.  The other probably was a cut-n-paste
error from another source.

I'll post a V2 shortly...

John
-- 
John W. LinvilleSomeday the world will need a hero, and you
linville at tuxdriver.com   might be all we have.  Be ready.

[dpdk-dev] Error while compiling DPDK

[BYEONG-GI KIM]

Dear Choi,

Of course I used "export RTE_TARGET=x86_64-default-linuxapp-gcc" when I was
trying to compile it.

By the way, the compilation went off to one more step, there was another
error message though;

== Build lib/librte_eal/linuxapp/kni
  LD
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/built-in.o
  CC [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/ixgbe_main.o
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/ixgbe_main.c:
In function 'ixgbe_del_mac_filter':
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/ixgbe_main.c:525:3:
error: implicit declaration of function 'compare_ether_addr'
[-Werror=implicit-function-declaration]
   if (!compare_ether_addr(addr, adapter->mac_table[i].addr) &&
   ^
cc1: all warnings being treated as errors
make[10]: ***
[/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni/ixgbe_main.o]
Error 1
make[9]: ***
[_module_/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/kni]
Error 2
make[8]: *** [sub-make] Error 2
make[7]: *** [rte_kni.ko] Error 2
make[6]: *** [kni] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [x86_64-default-linuxapp-gcc_install] Error 2
make: *** [install] Error 2

Honestly, I've never been able to compile DPDK successfully... I had been
trying to compile it on CentOS 6.5, and was failed. Then I changed OS from
CentOS to Fedora, but there are still lots of errors.

Best regards

Byeong-Gi KIM


2014-07-14 13:32 GMT+09:00 Choi, Sy Jong :

>  Hi Mr. Kim,
>
>
>
> If you are compiling x86_64-default-linuxapp-gcc
>
> The RTE_TARGET=x86_64-default-linuxapp-gcc
>
>
>
> I have manage to compile DPDK r1.6.0 with the following OS and kernel
> version
>
> CentOS with customer kernel
>
> Linux localhost.localdomain 3.3.1 #1 SMP Tue Jan 7 22:44:17 MYT 2014
> x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> Ubuntu 14.04
>
> Linux choi-desktop 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> May I know, have you been able to compile DPDK previously?
>
>
>
> Regards,
>
> Choi, Sy Jong
>
> Platform Application Engineer
>
>
>
> *From:* BYEONG-GI KIM [mailto:kimbyeonggi at gmail.com]
> *Sent:* Monday, July 14, 2014 11:29 AM
> *To:* Choi, Sy Jong; dev at dpdk.org; Dpdk-ovs at lists.01.org
>
> *Subject:* Re: [dpdk-dev] Error while compiling DPDK
>
>
>
> Dear Choi
>
>
>
> I used x86_64-default-linuxapp-gcc.
>
>
>
> I also checked x86_64-native-linuxapp-gcc after exporting
>  RTE_TARGET=x86_64-native-linuxapp-gcc, but there was a message "make[1]:
> Nothing to be done for `install'." while trying to install it.
>
>
>
> Best regards
>
>
>
> Byeong-Gi KIM
>
>
>
> 2014-07-14 11:40 GMT+09:00 Choi, Sy Jong :
>
> Hi Mr. Kim,
>
> May confirm which environment are you using?
> x86_64-default-linuxapp-gcc or
> x86_64-native-linuxapp-gcc
>
>
>
>
>
> Regards,
> Choi, Sy Jong
>
> -Original Message-
>
> *From: *BYEONG-GI KIM [kimbyeonggi at gmail.com]
> *Sent: *Monday, July 14, 2014 10:05 AM Malay Peninsula Standard Time
> *To: *Masaru Oki; dev at dpdk.org; Dpdk-ovs at lists.01.org
> *Subject: *Re: [dpdk-dev] Error while compiling DPDK
>
> Here is the error message in English;
>
> == Build lib/librte_eal/linuxapp
> == Build lib/librte_eal/linuxapp/igb_uio
>   LD
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
>   CC [M]
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
>   LD [M]
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
> INSTALL-MODULE igb_uio.ko
> == Build lib/librte_eal/linuxapp/eal
>   CC eal.o
> gcc: error: ?g: No such file or directory
> make[7]: *** [eal.o] Error 1
> make[6]: *** [eal] Error 2
> make[5]: *** [linuxapp] Error 2
> make[4]: *** [librte_eal] Error 2
> make[3]: *** [lib] Error 2
> make[2]: *** [all] Error 2
> make[1]: *** [x86_64-default-linuxapp-gcc_install] Error 2
> make: *** [install] Error 2
>
>
>
> 2014-07-14 11:02 GMT+09:00 Masaru Oki :
>
> > > I'm sorry for the Korean characteristics. It was shown because My
> Fedora
> > OS
> > > is set to use Korean as a default language.
> >
> > Try env LANG=C make install ...
> >
> >
> > 2014-07-14 10:24 GMT+09:00 BYEONG-GI KIM :
> >
> >> Dear choi,
> >>
> >> Thank you for the reply.
> >>
> >> I've been trying to install DPDK while changing the command as you
> >> mentioned, i.e., I used T=x86_64-default-linuxapp-gcc, but error was
> still
> >> shown;
> >>
> >>
> >> [root 

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

[John W. Linville]

On Mon, Jul 14, 2014 at 09:48:33AM -0400, John W. Linville wrote:
> On Fri, Jul 11, 2014 at 11:51:08PM +0100, Bruce Richardson wrote:
> > On Thu, Jul 10, 2014 at 04:32:49PM -0400, John W. Linville wrote:
> > > This is a Linux-specific virtual PMD driver backed by an AF_PACKET

> > I'm just trying this out now on a Fedora 20 machine, using kernel
> > 3.14.9-200.fc20.x86_64. However, while the first packet PMD port
> > initializes correctly, the subsequent ones do not. Please see output
> > from my test run below. All four ports are of the same type.
> 
> Thanks I'll check into it.  I'm not sure why you would only be able
> to set the fanout on the first port...

It looks like I lost a patch in the prep for posting.  As a result, I
was using the same fanout group ID between different interfaces... :-(

I'll post a V2 in a bit...thanks!

John
-- 
John W. LinvilleSomeday the world will need a hero, and you
linville at tuxdriver.com   might be all we have.  Be ready.

[dpdk-dev] No "pci_unbind.py" in tools subdirectory

[Aravind]

Hi,

You should be using igb_uio_bind.py , have a look at the quick start guide
: http://dpdk.org/doc/quick-start



On Mon, Jul 14, 2014 at 1:09 PM, BYEONG-GI KIM 
wrote:

> Hello.
>
> I'm sorry for the repeated question.
>
> I finally compiled DPDK successfully (there was a problem in the source
> code what I downloaded), and I'm moving to compile dpdk-ovs.
>
> Before compiling it, I'm trying to binding a network port to igb_uio
> module. In the dpdk-getting-started-guide, "pci_unbind.py" utility script
> is used to provide a view of the current state of the network ports on the
> system, and to bind/unbind those ports from the different kernel modules.
>
> The script, however, was not there in tools directory; There were only
> "igb_uio_bind.py". Is it fine as it is, or do I miss something?
>
> I downloaded the DPDK source from http://dpdk.org/browse/dpdk/refs/, and
> the file was dpdk-1.6.0r2.zip. I compiled both x86-64-defaultlinuxapp-gcc
> and x86-64-ivshmem-linuxapp-gcc now.
>
> Thanks in advance.
>
> Best regards
>
> Byeong-Gi KIM
>

[dpdk-dev] Error while compiling DPDK

[BYEONG-GI KIM]

Dear Choi

I used x86_64-default-linuxapp-gcc.

I also checked x86_64-native-linuxapp-gcc after exporting
 RTE_TARGET=x86_64-native-linuxapp-gcc, but there was a message "make[1]:
Nothing to be done for `install'." while trying to install it.

Best regards

Byeong-Gi KIM


2014-07-14 11:40 GMT+09:00 Choi, Sy Jong :

>  Hi Mr. Kim,
>
> May confirm which environment are you using?
> x86_64-default-linuxapp-gcc or
> x86_64-native-linuxapp-gcc
>
>
>
>
> Regards,
> Choi, Sy Jong
>
> -Original Message-
> *From: *BYEONG-GI KIM [kimbyeonggi at gmail.com]
> *Sent: *Monday, July 14, 2014 10:05 AM Malay Peninsula Standard Time
> *To: *Masaru Oki; dev at dpdk.org; Dpdk-ovs at lists.01.org
> *Subject: *Re: [dpdk-dev] Error while compiling DPDK
>
> Here is the error message in English;
>
> == Build lib/librte_eal/linuxapp
> == Build lib/librte_eal/linuxapp/igb_uio
>   LD
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
>   CC [M]
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
>   LD [M]
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
> INSTALL-MODULE igb_uio.ko
> == Build lib/librte_eal/linuxapp/eal
>   CC eal.o
> gcc: error: ?g: No such file or directory
> make[7]: *** [eal.o] Error 1
> make[6]: *** [eal] Error 2
> make[5]: *** [linuxapp] Error 2
> make[4]: *** [librte_eal] Error 2
> make[3]: *** [lib] Error 2
> make[2]: *** [all] Error 2
> make[1]: *** [x86_64-default-linuxapp-gcc_install] Error 2
> make: *** [install] Error 2
>
>
>
> 2014-07-14 11:02 GMT+09:00 Masaru Oki :
>
> > > I'm sorry for the Korean characteristics. It was shown because My
> Fedora
> > OS
> > > is set to use Korean as a default language.
> >
> > Try env LANG=C make install ...
> >
> >
> > 2014-07-14 10:24 GMT+09:00 BYEONG-GI KIM :
> >
> >> Dear choi,
> >>
> >> Thank you for the reply.
> >>
> >> I've been trying to install DPDK while changing the command as you
> >> mentioned, i.e., I used T=x86_64-default-linuxapp-gcc, but error was
> still
> >> shown;
> >>
> >>
> >> [root at compute DPDK-1.6.0]# make install T=x86_64-default-linuxapp-gcc
> >> == Installing x86_64-default-linuxapp-gcc
> >> Configuration done
> >> == Build scripts
> >> == Build scripts/testhost
> >>   HOSTCC testhost.o
> >>   HOSTLD testhost
> >>   INSTALL-HOSTAPP testhost
> >> == Build lib
> >> == Build lib/librte_eal
> >> == Build lib/librte_eal/common
> >>   SYMLINK-FILE include/rte_atomic.h
> >>   SYMLINK-FILE include/rte_branch_prediction.h
> >>   SYMLINK-FILE include/rte_byteorder.h
> >>   SYMLINK-FILE include/rte_common.h
> >>   SYMLINK-FILE include/rte_cycles.h
> >>   SYMLINK-FILE include/rte_debug.h
> >>   SYMLINK-FILE include/rte_eal.h
> >>   SYMLINK-FILE include/rte_errno.h
> >>   SYMLINK-FILE include/rte_launch.h
> >>   SYMLINK-FILE include/rte_lcore.h
> >>   SYMLINK-FILE include/rte_log.h
> >>   SYMLINK-FILE include/rte_memcpy.h
> >>   SYMLINK-FILE include/rte_memory.h
> >>   SYMLINK-FILE include/rte_memzone.h
> >>   SYMLINK-FILE include/rte_pci.h
> >>   SYMLINK-FILE include/rte_pci_dev_ids.h
> >>   SYMLINK-FILE include/rte_per_lcore.h
> >>   SYMLINK-FILE include/rte_prefetch.h
> >>   SYMLINK-FILE include/rte_random.h
> >>   SYMLINK-FILE include/rte_rwlock.h
> >>   SYMLINK-FILE include/rte_spinlock.h
> >>   SYMLINK-FILE include/rte_tailq.h
> >>   SYMLINK-FILE include/rte_interrupts.h
> >>   SYMLINK-FILE include/rte_alarm.h
> >>   SYMLINK-FILE include/rte_string_fns.h
> >>   SYMLINK-FILE include/rte_cpuflags.h
> >>   SYMLINK-FILE include/rte_version.h
> >>   SYMLINK-FILE include/rte_tailq_elem.h
> >>   SYMLINK-FILE include/rte_eal_memconfig.h
> >>   SYMLINK-FILE include/rte_malloc_heap.h
> >>   SYMLINK-FILE include/rte_hexdump.h
> >>   SYMLINK-FILE include/arch/rte_atomic.h
> >> == Build lib/librte_eal/linuxapp
> >> == Build lib/librte_eal/linuxapp/igb_uio
> >>   LD
> >>
> >>
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
> >>   CC [M]
> >>
> >>
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
> >>   Building modules, stage 2.
> >>   MODPOST 1 modules
> >>   CC
> >>
> >>
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
> >>   LD [M]
> >>
> >>
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
> >> INSTALL-MODULE igb_uio.ko
> >> == Build lib/librte_eal/linuxapp/eal
> >>   CC eal.o
> >> gcc: error: ?g: ??  ? 
> >> make[7]: *** [eal.o] ?? 1
> >> make[6]: *** [eal] ?? 2
> >> make[5]: *** [linuxapp] ?? 2
> >> make[4]: *** [librte_eal] ?? 2
> 

[dpdk-dev] Error while compiling DPDK

[BYEONG-GI KIM]

Here is the error message in English;

== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/igb_uio
  LD
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
  CC [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
  LD [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
INSTALL-MODULE igb_uio.ko
== Build lib/librte_eal/linuxapp/eal
  CC eal.o
gcc: error: ?g: No such file or directory
make[7]: *** [eal.o] Error 1
make[6]: *** [eal] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [x86_64-default-linuxapp-gcc_install] Error 2
make: *** [install] Error 2



2014-07-14 11:02 GMT+09:00 Masaru Oki :

> > I'm sorry for the Korean characteristics. It was shown because My Fedora
> OS
> > is set to use Korean as a default language.
>
> Try env LANG=C make install ...
>
>
> 2014-07-14 10:24 GMT+09:00 BYEONG-GI KIM :
>
>> Dear choi,
>>
>> Thank you for the reply.
>>
>> I've been trying to install DPDK while changing the command as you
>> mentioned, i.e., I used T=x86_64-default-linuxapp-gcc, but error was still
>> shown;
>>
>>
>> [root at compute DPDK-1.6.0]# make install T=x86_64-default-linuxapp-gcc
>> == Installing x86_64-default-linuxapp-gcc
>> Configuration done
>> == Build scripts
>> == Build scripts/testhost
>>   HOSTCC testhost.o
>>   HOSTLD testhost
>>   INSTALL-HOSTAPP testhost
>> == Build lib
>> == Build lib/librte_eal
>> == Build lib/librte_eal/common
>>   SYMLINK-FILE include/rte_atomic.h
>>   SYMLINK-FILE include/rte_branch_prediction.h
>>   SYMLINK-FILE include/rte_byteorder.h
>>   SYMLINK-FILE include/rte_common.h
>>   SYMLINK-FILE include/rte_cycles.h
>>   SYMLINK-FILE include/rte_debug.h
>>   SYMLINK-FILE include/rte_eal.h
>>   SYMLINK-FILE include/rte_errno.h
>>   SYMLINK-FILE include/rte_launch.h
>>   SYMLINK-FILE include/rte_lcore.h
>>   SYMLINK-FILE include/rte_log.h
>>   SYMLINK-FILE include/rte_memcpy.h
>>   SYMLINK-FILE include/rte_memory.h
>>   SYMLINK-FILE include/rte_memzone.h
>>   SYMLINK-FILE include/rte_pci.h
>>   SYMLINK-FILE include/rte_pci_dev_ids.h
>>   SYMLINK-FILE include/rte_per_lcore.h
>>   SYMLINK-FILE include/rte_prefetch.h
>>   SYMLINK-FILE include/rte_random.h
>>   SYMLINK-FILE include/rte_rwlock.h
>>   SYMLINK-FILE include/rte_spinlock.h
>>   SYMLINK-FILE include/rte_tailq.h
>>   SYMLINK-FILE include/rte_interrupts.h
>>   SYMLINK-FILE include/rte_alarm.h
>>   SYMLINK-FILE include/rte_string_fns.h
>>   SYMLINK-FILE include/rte_cpuflags.h
>>   SYMLINK-FILE include/rte_version.h
>>   SYMLINK-FILE include/rte_tailq_elem.h
>>   SYMLINK-FILE include/rte_eal_memconfig.h
>>   SYMLINK-FILE include/rte_malloc_heap.h
>>   SYMLINK-FILE include/rte_hexdump.h
>>   SYMLINK-FILE include/arch/rte_atomic.h
>> == Build lib/librte_eal/linuxapp
>> == Build lib/librte_eal/linuxapp/igb_uio
>>   LD
>>
>>  
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
>>   CC [M]
>>
>>  
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
>>   Building modules, stage 2.
>>   MODPOST 1 modules
>>   CC
>>
>>  
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
>>   LD [M]
>>
>>  
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
>> INSTALL-MODULE igb_uio.ko
>> == Build lib/librte_eal/linuxapp/eal
>>   CC eal.o
>> gcc: error: ?g: ??  ? 
>> make[7]: *** [eal.o] ?? 1
>> make[6]: *** [eal] ?? 2
>> make[5]: *** [linuxapp] ?? 2
>> make[4]: *** [librte_eal] ?? 2
>> make[3]: *** [lib] ?? 2
>> make[2]: *** [all] ?? 2
>> make[1]: *** [x86_64-default-linuxapp-gcc_install] ?? 2
>> make: *** [install] ?? 2
>>
>> I'm sorry for the Korean characteristics. It was shown because My Fedora
>> OS
>> is set to use Korean as a default language.
>>
>> I set two environmental variables following the
>> intel-dpdk-programmers-guide.pdf as below:
>>
>> export RTE_SDK=/home/stack/dpdk/DPDK-1.6.0
>> export RTE_TARGET=x86_64-native-linuxapp-gcc
>>
>> What should I do in order to install DPDK successfully?...
>>
>> Thanks in advance.
>>
>> Best regards
>>
>> Byeong-Gi KIM
>>
>>
>>
>>
>> 2014-07-14 10:00 GMT+09:00 Choi, Sy Jong :
>>
>> >  Hi Mr. Kim,
>> >
>> > Please do not compile with "T=x86*gcc" because it will compile BSD app
>> > too, which cause the error.
>> >
>> > Please complile only the configuration you need. This should remove the
>> > error.
>> >
>> >
>> > Regards,
>> > Choi, Sy Jong
>> >
>> >
>> > -Original Message-
>> > *From: 

[dpdk-dev] Error while compiling DPDK

[Masaru Oki]

> I'm sorry for the Korean characteristics. It was shown because My Fedora
OS
> is set to use Korean as a default language.

Try env LANG=C make install ...


2014-07-14 10:24 GMT+09:00 BYEONG-GI KIM :

> Dear choi,
>
> Thank you for the reply.
>
> I've been trying to install DPDK while changing the command as you
> mentioned, i.e., I used T=x86_64-default-linuxapp-gcc, but error was still
> shown;
>
>
> [root at compute DPDK-1.6.0]# make install T=x86_64-default-linuxapp-gcc
> == Installing x86_64-default-linuxapp-gcc
> Configuration done
> == Build scripts
> == Build scripts/testhost
>   HOSTCC testhost.o
>   HOSTLD testhost
>   INSTALL-HOSTAPP testhost
> == Build lib
> == Build lib/librte_eal
> == Build lib/librte_eal/common
>   SYMLINK-FILE include/rte_atomic.h
>   SYMLINK-FILE include/rte_branch_prediction.h
>   SYMLINK-FILE include/rte_byteorder.h
>   SYMLINK-FILE include/rte_common.h
>   SYMLINK-FILE include/rte_cycles.h
>   SYMLINK-FILE include/rte_debug.h
>   SYMLINK-FILE include/rte_eal.h
>   SYMLINK-FILE include/rte_errno.h
>   SYMLINK-FILE include/rte_launch.h
>   SYMLINK-FILE include/rte_lcore.h
>   SYMLINK-FILE include/rte_log.h
>   SYMLINK-FILE include/rte_memcpy.h
>   SYMLINK-FILE include/rte_memory.h
>   SYMLINK-FILE include/rte_memzone.h
>   SYMLINK-FILE include/rte_pci.h
>   SYMLINK-FILE include/rte_pci_dev_ids.h
>   SYMLINK-FILE include/rte_per_lcore.h
>   SYMLINK-FILE include/rte_prefetch.h
>   SYMLINK-FILE include/rte_random.h
>   SYMLINK-FILE include/rte_rwlock.h
>   SYMLINK-FILE include/rte_spinlock.h
>   SYMLINK-FILE include/rte_tailq.h
>   SYMLINK-FILE include/rte_interrupts.h
>   SYMLINK-FILE include/rte_alarm.h
>   SYMLINK-FILE include/rte_string_fns.h
>   SYMLINK-FILE include/rte_cpuflags.h
>   SYMLINK-FILE include/rte_version.h
>   SYMLINK-FILE include/rte_tailq_elem.h
>   SYMLINK-FILE include/rte_eal_memconfig.h
>   SYMLINK-FILE include/rte_malloc_heap.h
>   SYMLINK-FILE include/rte_hexdump.h
>   SYMLINK-FILE include/arch/rte_atomic.h
> == Build lib/librte_eal/linuxapp
> == Build lib/librte_eal/linuxapp/igb_uio
>   LD
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
>   CC [M]
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
>   Building modules, stage 2.
>   MODPOST 1 modules
>   CC
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
>   LD [M]
>
>  
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
> INSTALL-MODULE igb_uio.ko
> == Build lib/librte_eal/linuxapp/eal
>   CC eal.o
> gcc: error: ?g: ??  ? 
> make[7]: *** [eal.o] ?? 1
> make[6]: *** [eal] ?? 2
> make[5]: *** [linuxapp] ?? 2
> make[4]: *** [librte_eal] ?? 2
> make[3]: *** [lib] ?? 2
> make[2]: *** [all] ?? 2
> make[1]: *** [x86_64-default-linuxapp-gcc_install] ?? 2
> make: *** [install] ?? 2
>
> I'm sorry for the Korean characteristics. It was shown because My Fedora OS
> is set to use Korean as a default language.
>
> I set two environmental variables following the
> intel-dpdk-programmers-guide.pdf as below:
>
> export RTE_SDK=/home/stack/dpdk/DPDK-1.6.0
> export RTE_TARGET=x86_64-native-linuxapp-gcc
>
> What should I do in order to install DPDK successfully?...
>
> Thanks in advance.
>
> Best regards
>
> Byeong-Gi KIM
>
>
>
>
> 2014-07-14 10:00 GMT+09:00 Choi, Sy Jong :
>
> >  Hi Mr. Kim,
> >
> > Please do not compile with "T=x86*gcc" because it will compile BSD app
> > too, which cause the error.
> >
> > Please complile only the configuration you need. This should remove the
> > error.
> >
> >
> > Regards,
> > Choi, Sy Jong
> >
> >
> > -Original Message-
> > *From: *BYEONG-GI KIM [kimbyeonggi at gmail.com]
> > *Sent: *Monday, July 14, 2014 08:25 AM Malay Peninsula Standard Time
> > *To: *Dpdk-ovs at lists.01.org; dev at dpdk.org
> > *Subject: *[dpdk-dev] Error while compiling DPDK
> >
> > Hello.
> >
> > An error occured while compiling DPDK 1.6.0r2 as below:
> >
> > [root at compute dpdk-1.6.0r2]# make install T=x86_64*gcc
> > ...Installing...
> > /ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c: In function
> > ?rte_eal_init?:
> > /ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c:873:2: error:
> > format ?%p? expects argument of type ?void *?, but argument 5 has type
> > ?pthread_t? [-Werror=format=]
> >   RTE_LOG(DEBUG, EAL, "Master core %u is ready (tid=%p)\n",
> >   ^
> >
> > The current OS is Fedora20. What should I do?...
> >
> > Best regards
> >
> > Byeong-Gi KIM
> >
>

[dpdk-dev] Hardware Offloads Support for VF

[Alex Markuze]

Hi,
I have a Virtual setup with an Intel 82599 NIC (VF).

I'm trying to Disable CRC stripping, and the flag is gracefully ignored.
This seems to be documented In the DPDK June Release notes (6.16).

Are these limitations (Jumbo Frames, CRC Stripping , Checksum ) are a NIC
(HW/FW)limitations? Or is this something that can be resolved in SW to
allow separate per VF configuration?

Thanks.

[dpdk-dev] Error while compiling DPDK

[BYEONG-GI KIM]

Dear choi,

Thank you for the reply.

I've been trying to install DPDK while changing the command as you
mentioned, i.e., I used T=x86_64-default-linuxapp-gcc, but error was still
shown;


[root at compute DPDK-1.6.0]# make install T=x86_64-default-linuxapp-gcc
== Installing x86_64-default-linuxapp-gcc
Configuration done
== Build scripts
== Build scripts/testhost
  HOSTCC testhost.o
  HOSTLD testhost
  INSTALL-HOSTAPP testhost
== Build lib
== Build lib/librte_eal
== Build lib/librte_eal/common
  SYMLINK-FILE include/rte_atomic.h
  SYMLINK-FILE include/rte_branch_prediction.h
  SYMLINK-FILE include/rte_byteorder.h
  SYMLINK-FILE include/rte_common.h
  SYMLINK-FILE include/rte_cycles.h
  SYMLINK-FILE include/rte_debug.h
  SYMLINK-FILE include/rte_eal.h
  SYMLINK-FILE include/rte_errno.h
  SYMLINK-FILE include/rte_launch.h
  SYMLINK-FILE include/rte_lcore.h
  SYMLINK-FILE include/rte_log.h
  SYMLINK-FILE include/rte_memcpy.h
  SYMLINK-FILE include/rte_memory.h
  SYMLINK-FILE include/rte_memzone.h
  SYMLINK-FILE include/rte_pci.h
  SYMLINK-FILE include/rte_pci_dev_ids.h
  SYMLINK-FILE include/rte_per_lcore.h
  SYMLINK-FILE include/rte_prefetch.h
  SYMLINK-FILE include/rte_random.h
  SYMLINK-FILE include/rte_rwlock.h
  SYMLINK-FILE include/rte_spinlock.h
  SYMLINK-FILE include/rte_tailq.h
  SYMLINK-FILE include/rte_interrupts.h
  SYMLINK-FILE include/rte_alarm.h
  SYMLINK-FILE include/rte_string_fns.h
  SYMLINK-FILE include/rte_cpuflags.h
  SYMLINK-FILE include/rte_version.h
  SYMLINK-FILE include/rte_tailq_elem.h
  SYMLINK-FILE include/rte_eal_memconfig.h
  SYMLINK-FILE include/rte_malloc_heap.h
  SYMLINK-FILE include/rte_hexdump.h
  SYMLINK-FILE include/arch/rte_atomic.h
== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/igb_uio
  LD
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
  CC [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
  LD [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
INSTALL-MODULE igb_uio.ko
== Build lib/librte_eal/linuxapp/eal
  CC eal.o
gcc: error: ?g: ??  ? 
make[7]: *** [eal.o] ?? 1
make[6]: *** [eal] ?? 2
make[5]: *** [linuxapp] ?? 2
make[4]: *** [librte_eal] ?? 2
make[3]: *** [lib] ?? 2
make[2]: *** [all] ?? 2
make[1]: *** [x86_64-default-linuxapp-gcc_install] ?? 2
make: *** [install] ?? 2

I'm sorry for the Korean characteristics. It was shown because My Fedora OS
is set to use Korean as a default language.

I set two environmental variables following the
intel-dpdk-programmers-guide.pdf as below:

export RTE_SDK=/home/stack/dpdk/DPDK-1.6.0
export RTE_TARGET=x86_64-native-linuxapp-gcc

What should I do in order to install DPDK successfully?...

Thanks in advance.

Best regards

Byeong-Gi KIM




2014-07-14 10:00 GMT+09:00 Choi, Sy Jong :

>  Hi Mr. Kim,
>
> Please do not compile with "T=x86*gcc" because it will compile BSD app
> too, which cause the error.
>
> Please complile only the configuration you need. This should remove the
> error.
>
>
> Regards,
> Choi, Sy Jong
>
>
> -Original Message-
> *From: *BYEONG-GI KIM [kimbyeonggi at gmail.com]
> *Sent: *Monday, July 14, 2014 08:25 AM Malay Peninsula Standard Time
> *To: *Dpdk-ovs at lists.01.org; dev at dpdk.org
> *Subject: *[dpdk-dev] Error while compiling DPDK
>
> Hello.
>
> An error occured while compiling DPDK 1.6.0r2 as below:
>
> [root at compute dpdk-1.6.0r2]# make install T=x86_64*gcc
> ...Installing...
> /ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c: In function
> ?rte_eal_init?:
> /ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c:873:2: error:
> format ?%p? expects argument of type ?void *?, but argument 5 has type
> ?pthread_t? [-Werror=format=]
>   RTE_LOG(DEBUG, EAL, "Master core %u is ready (tid=%p)\n",
>   ^
>
> The current OS is Fedora20. What should I do?...
>
> Best regards
>
> Byeong-Gi KIM
>

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

[John W. Linville]

On Fri, Jul 11, 2014 at 11:51:08PM +0100, Bruce Richardson wrote:
> On Thu, Jul 10, 2014 at 04:32:49PM -0400, John W. Linville wrote:
> > 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.
> > 
> Hi John,
> 
> I'm just trying this out now on a Fedora 20 machine, using kernel 
> 3.14.9-200.fc20.x86_64. However, while the first packet PMD port initializes 
> correctly, the subsequent ones do not. Please see output from my test run 
> below. All four ports are of the same type.

Thanks I'll check into it.  I'm not sure why you would only be able
to set the fanout on the first port...

> 
> Regards,
> /Bruce
> 
> bruce at silpixa00372841:dpdk.org$ sudo 
> ./x86_64-native-linuxapp-gcc/app/testpmd -c 600 -n 4 
> --vdev=eth_packet0,iface=eth0,qpairs=1 --vdev=eth_packet1,iface=eth1,qpairs=1 
> --vdev=eth_packet2,iface=p802p1,qpairs=1 
> --vdev=eth_packet3,iface=p9p3,qpairs=1 -- --mbcache=250 --burst=32 
> --total-num-mbufs=65536EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Detected lcore 4 as core 4 on socket 0
> EAL: Detected lcore 5 as core 5 on socket 0
> EAL: Detected lcore 6 as core 6 on socket 0
> EAL: Detected lcore 7 as core 7 on socket 0
> EAL: Detected lcore 8 as core 0 on socket 1
> EAL: Detected lcore 9 as core 1 on socket 1
> EAL: Detected lcore 10 as core 2 on socket 1
> EAL: Detected lcore 11 as core 3 on socket 1
> EAL: Detected lcore 12 as core 4 on socket 1
> EAL: Detected lcore 13 as core 5 on socket 1
> EAL: Detected lcore 14 as core 6 on socket 1
> EAL: Detected lcore 15 as core 7 on socket 1
> EAL: Detected lcore 16 as core 0 on socket 0
> EAL: Detected lcore 17 as core 1 on socket 0
> EAL: Detected lcore 18 as core 2 on socket 0
> EAL: Detected lcore 19 as core 3 on socket 0
> EAL: Detected lcore 20 as core 4 on socket 0
> EAL: Detected lcore 21 as core 5 on socket 0
> EAL: Detected lcore 22 as core 6 on socket 0
> EAL: Detected lcore 23 as core 7 on socket 0
> EAL: Detected lcore 24 as core 0 on socket 1
> EAL: Detected lcore 25 as core 1 on socket 1
> EAL: Detected lcore 26 as core 2 on socket 1
> EAL: Detected lcore 27 as core 3 on socket 1
> EAL: Detected lcore 28 as core 4 on socket 1
> EAL: Detected lcore 29 as core 5 on socket 1
> EAL: Detected lcore 30 as core 6 on socket 1
> EAL: Detected lcore 31 as core 7 on socket 1
> EAL: Support maximum 64 logical core(s) by configuration.
> EAL: Detected 32 lcore(s)
> EAL: No free hugepages reported in hugepages-2048kB
> EAL:   unsupported IOMMU type!
> EAL: VFIO support could not be initialized
> EAL: Setting up memory...
> EAL: Ask a virtual area of 0x8000 bytes
> EAL: Virtual area found at 0x7f9fc000 (size = 0x8000)
> EAL: Ask a virtual area of 0x8000 bytes
> EAL: Virtual area found at 0x7f9f (size = 0x8000)
> EAL: Requesting 2 pages of size 1024MB from socket 0
> EAL: Requesting 2 pages of size 1024MB from socket 1
> EAL: TSC frequency is ~2693512 KHz
> EAL: Master core 9 is ready (tid=f4511880)
> init (0) eth_packet0
> PMD: Initializing pmd_packet for eth_packet0
> PMD: eth_packet0: AF_PACKET MMAP parameters:
> PMD: eth_packet0: block size 4096
> PMD: eth_packet0: block count 256
> PMD: eth_packet0: frame size 2048
> PMD: eth_packet0: frame count 512
> PMD: eth_packet0: creating AF_PACKET-backed ethdev on numa socket 1
> init (0) eth_packet1
> PMD: Initializing pmd_packet for eth_packet1
> PMD: eth_packet1: AF_PACKET MMAP parameters:
> PMD: eth_packet1: block size 4096
> PMD: eth_packet1: block count 256
> PMD: eth_packet1: frame size 2048
> PMD: eth_packet1: frame count 512
> 

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

[John W. Linville]

On Sat, Jul 12, 2014 at 12:42:04AM +, Zhou, Danny wrote:
> I just upgraded my kernel to 3.15.5 and hardcoded below captured from 
> include/uapi/linux/if_packet.h to librte_pmd_packet.c to workaround it, now I 
> can receive/transmit packet now. Commenting out PACKET_FANOUT_FLAG_ROLLOVER 
> would cause no packet can be received. 
> 
> #define PACKET_QDISC_BYPASS 20
> #define PACKET_FANOUT_FLAG_ROLLOVER 0x1000

You shouldn't need PACKET_FANOUT_FLAG_ROLLOVER if all the queues are
being used.  Does the application you are running make use of all
the queues?  If not, you probably should use the qpairs option to
limit the number of queues created by the eth_packet PMD.

John

> 
> > -Original Message-
> > From: John W. Linville [mailto:linville at tuxdriver.com]
> > Sent: Saturday, July 12, 2014 2:47 AM
> > To: Zhou, Danny
> > Cc: dev at dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH] librte_pmd_packet: add PMD for
> > AF_PACKET-based virtual devices
> > 
> > Not sure what the issue might be, PACKET_FANOUT_FLAG_ROLLOVER is defined
> > in include/uapi/linux/if_packet.h in the v3.12 tree.
> > 
> > On Fri, Jul 11, 2014 at 06:01:27PM +, Zhou, Danny wrote:
> > > Tried on 3.12, both of them are undefined. Anyway, will comment them out 
> > > and see
> > what performance it could achieve.
> > >
> > > > -Original Message-
> > > > From: John W. Linville [mailto:linville at tuxdriver.com]
> > > > Sent: Saturday, July 12, 2014 1:41 AM
> > > > To: Zhou, Danny
> > > > Cc: dev at dpdk.org
> > > > Subject: Re: [dpdk-dev] [PATCH] librte_pmd_packet: add PMD for
> > > > AF_PACKET-based virtual devices
> > > >
> > > > On Fri, Jul 11, 2014 at 05:20:42PM +, Zhou, Danny wrote:
> > > > > Looks like you used a pretty new kernel version with new socket
> > > > > options that old
> > > > kernel like my 3.12 does not support. When I tried this patch, it
> > > > just cannot build, and compiler complains like below. Which Linux 
> > > > distribution
> > does this patch work for?
> > > > How to ensure it works for old kernels?
> > > > >
> > > > > /home/danny/dpdk.org/dpdk/lib/librte_pmd_packet/rte_eth_packet.c:
> > > > > In function
> > > > rte_pmd_init_internals:
> > > > > /home/danny/dpdk.org/dpdk/lib/librte_pmd_packet/rte_eth_packet.c:5
> > > > > 24:1
> > > > > 7: error: PACKET_FANOUT_FLAG_ROLLOVER undeclared (first use in
> > > > > this
> > > > > function)
> > > > > /home/danny/dpdk.org/dpdk/lib/librte_pmd_packet/rte_eth_packet.c:5
> > > > > 24:1
> > > > > 7: note: each undeclared identifier is reported only once for each
> > > > > function it appears in
> > > > > /home/danny/dpdk.org/dpdk/lib/librte_pmd_packet/rte_eth_packet.c:5
> > > > > 57:3
> > > > > 3: error: PACKET_QDISC_BYPASS undeclared (first use in this
> > > > > function)
> > > >
> > > > Both of them are isolated, so for playing with it you could just 
> > > > comment those
> > out.
> > > > It looks like PACKET_FANOUT_FLAG_ROLLOVER should have been in 3.10,
> > > > while PACKET_QDISC_BYPASS didn't show-up until 3.14...
> > > >
> > > > /home/linville/git/linux
> > > > [linville-x1.hq.tuxdriver.com]:> git annotate
> > > > include/uapi/linux/if_packet.h | grep PACKET_FANOUT_FLAG_ROLLOVER
> > > > 77f65ebdca506   (Willem de Bruijn   2013-03-19 10:18:11 +   
> > > > 64)#define
> > > > PACKET_FANOUT_FLAG_ROLLOVER 0x1000
> > > >
> > > > /home/linville/git/linux
> > > > [linville-x1.hq.tuxdriver.com]:> git show -s --format=short
> > > > 77f65ebdca506 commit 77f65ebdca506870d99bfabe52bde222511022ec
> > > > Author: Willem de Bruijn 
> > > >
> > > > packet: packet fanout rollover during socket overload
> > > >
> > > > /home/linville/git/linux
> > > > [linville-x1.hq.tuxdriver.com]:> git describe --contains
> > > > 77f65ebdca506
> > > > v3.10-rc1~66^2~423
> > > >
> > > > /home/linville/git/linux
> > > > [linville-x1.hq.tuxdriver.com]:> git annotate
> > > > include/uapi/linux/if_packet.h | grep PACKET_QDISC_BYPASS
> > > > d346a3fae3ff1   (Daniel Borkmann2013-12-06 11:36:17 +0100   
> > > > 56)#define
> > > > PACKET_QDISC_BYPASS 20
> > > >
> > > > /home/linville/git/linux
> > > > [linville-x1.hq.tuxdriver.com]:> git show -s --format=short
> > > > d346a3fae3ff1 commit
> > > > d346a3fae3ff1d99f5d0c819bf86edf9094a26a1
> > > > Author: Daniel Borkmann 
> > > >
> > > > packet: introduce PACKET_QDISC_BYPASS socket option
> > > >
> > > > /home/linville/git/linux
> > > > [linville-x1.hq.tuxdriver.com]:> git describe --contains
> > > > d346a3fae3ff1
> > > > v3.14-rc1~94^2~564
> > > >
> > > > Is there an example of code in DPDK that requires specific kernel
> > > > versions?  What is the preferred method for coding such dependencies?
> > > >
> > > > John
> > > > --
> > > > John W. LinvilleSomeday the world will need a hero, and 
> > > > you
> > > > linville at tuxdriver.com   might be all we have.  
> > > > Be ready.
> > >
> > 
> > --
> > John W. LinvilleSomeday the 

[dpdk-dev] Error while compiling DPDK

[BYEONG-GI KIM]

Hello.

An error occured while compiling DPDK 1.6.0r2 as below:

[root at compute dpdk-1.6.0r2]# make install T=x86_64*gcc
...Installing...
/ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c: In function
?rte_eal_init?:
/ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c:873:2: error:
format ?%p? expects argument of type ?void *?, but argument 5 has type
?pthread_t? [-Werror=format=]
  RTE_LOG(DEBUG, EAL, "Master core %u is ready (tid=%p)\n",
  ^

The current OS is Fedora20. What should I do?...

Best regards

Byeong-Gi KIM

[dpdk-dev] [Dpdk-ovs] No "pci_unbind.py" in tools subdirectory

[Choi, Sy Jong]

Hi Mr. Kim,

I think DPDK r1.6 from dpdk.org has change certain file naming. I think it is 
ok to use the igb_uio_bind.py.
Sometime, I would modprobe ?r ixgbe to remove some confusion on the binding. 
And only load igb_uio.ko from DPDK.


Regards,
Choi, Sy Jong
Platform Application Engineer

From: Dpdk-ovs [mailto:dpdk-ovs-boun...@lists.01.org] On Behalf Of BYEONG-GI KIM
Sent: Monday, July 14, 2014 3:39 PM
To: Dpdk-ovs at lists.01.org; dev at dpdk.org
Subject: [Dpdk-ovs] No "pci_unbind.py" in tools subdirectory

Hello.

I'm sorry for the repeated question.

I finally compiled DPDK successfully (there was a problem in the source code 
what I downloaded), and I'm moving to compile dpdk-ovs.

Before compiling it, I'm trying to binding a network port to igb_uio module. In 
the dpdk-getting-started-guide, "pci_unbind.py" utility script is used to 
provide a view of the current state of the network ports on the system, and to 
bind/unbind those ports from the different kernel modules.

The script, however, was not there in tools directory; There were only 
"igb_uio_bind.py". Is it fine as it is, or do I miss something?

I downloaded the DPDK source from http://dpdk.org/browse/dpdk/refs/, and the 
file was dpdk-1.6.0r2.zip. I compiled both x86-64-defaultlinuxapp-gcc and 
x86-64-ivshmem-linuxapp-gcc now.

Thanks in advance.

Best regards

Byeong-Gi KIM

[dpdk-dev] Error while compiling DPDK

[De Lara Guarch, Pablo]

Hi Byeong-gi,

> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of BYEONG-GI KIM
> Sent: Monday, July 14, 2014 5:44 AM
> To: Choi, Sy Jong; Dpdk-ovs at lists.01.org; dev at dpdk.org
> Subject: Re: [dpdk-dev] Error while compiling DPDK
> 
> Dear Choi,
> 
> Of course I used "export RTE_TARGET=x86_64-default-linuxapp-gcc" when I was
> trying to compile it.
> 
> By the way, the compilation went off to one more step, there was another
> error message though;
> 
> == Build lib/librte_eal/linuxapp/kni
>   LD
>  /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-
> gcc/build/lib/librte_eal/linuxapp/kni/built-in.o
>   CC [M]
>  /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-
> gcc/build/lib/librte_eal/linuxapp/kni/ixgbe_main.o
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-
> gcc/build/lib/librte_eal/linuxapp/kni/ixgbe_main.c:
> In function 'ixgbe_del_mac_filter':
> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-
> gcc/build/lib/librte_eal/linuxapp/kni/ixgbe_main.c:525:3:
> error: implicit declaration of function 'compare_ether_addr'
> [-Werror=implicit-function-declaration]
>if (!compare_ether_addr(addr, adapter->mac_table[i].addr) &&
>^
> cc1: all warnings being treated as errors
> make[10]: ***
> [/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-
> gcc/build/lib/librte_eal/linuxapp/kni/ixgbe_main.o]
> Error 1
> make[9]: ***
> [_module_/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-
> gcc/build/lib/librte_eal/linuxapp/kni]
> Error 2
> make[8]: *** [sub-make] Error 2
> make[7]: *** [rte_kni.ko] Error 2
> make[6]: *** [kni] Error 2
> make[5]: *** [linuxapp] Error 2
> make[4]: *** [librte_eal] Error 2
> make[3]: *** [lib] Error 2
> make[2]: *** [all] Error 2
> make[1]: *** [x86_64-default-linuxapp-gcc_install] Error 2
> make: *** [install] Error 2
> 
> Honestly, I've never been able to compile DPDK successfully... I had been
> trying to compile it on CentOS 6.5, and was failed. Then I changed OS from
> CentOS to Fedora, but there are still lots of errors.
> 
> Best regards
> 
> Byeong-Gi KIM

To compile DPDK, you don't need to export RTE_TARGET, that's just for apps.
Anyway, have you tried to compile the latest dpdk version? Just remember to 
use different target: x86_64-native-linuxapp-gcc.

Regards,
Pablo

[dpdk-dev] Hardware Offloads Support for VF

[Zhang, Helin]

> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Alex Markuze
> Sent: Monday, July 14, 2014 3:53 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] Hardware Offloads Support for VF
> 
> Hi,
> I have a Virtual setup with an Intel 82599 NIC (VF).
> 
> I'm trying to Disable CRC stripping, and the flag is gracefully ignored.
> This seems to be documented In the DPDK June Release notes (6.16).
> 
> Are these limitations (Jumbo Frames, CRC Stripping , Checksum ) are a NIC
> (HW/FW)limitations? Or is this something that can be resolved in SW to allow
> separate per VF configuration?
> 
> Thanks.

Hi Alex

For 82599, it is controlled by a register to globally enable or disable that. 
This can only done in PF side, it is not reasonable to do that in VF.

In addition, i40e or else might be different.

Regards,
Helin

[dpdk-dev] Error while compiling DPDK

[Choi, Sy Jong]

Hi Mr. Kim,

If you are compiling x86_64-default-linuxapp-gcc
The RTE_TARGET=x86_64-default-linuxapp-gcc

I have manage to compile DPDK r1.6.0 with the following OS and kernel version
CentOS with customer kernel
Linux localhost.localdomain 3.3.1 #1 SMP Tue Jan 7 22:44:17 MYT 2014 x86_64 
x86_64 x86_64 GNU/Linux

Ubuntu 14.04
Linux choi-desktop 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

May I know, have you been able to compile DPDK previously?

Regards,
Choi, Sy Jong
Platform Application Engineer

From: BYEONG-GI KIM [mailto:kimbyeon...@gmail.com]
Sent: Monday, July 14, 2014 11:29 AM
To: Choi, Sy Jong; dev at dpdk.org; Dpdk-ovs at lists.01.org
Subject: Re: [dpdk-dev] Error while compiling DPDK

Dear Choi

I used x86_64-default-linuxapp-gcc.

I also checked x86_64-native-linuxapp-gcc after exporting  
RTE_TARGET=x86_64-native-linuxapp-gcc, but there was a message "make[1]: 
Nothing to be done for `install'." while trying to install it.

Best regards

Byeong-Gi KIM

2014-07-14 11:40 GMT+09:00 Choi, Sy Jong mailto:sy.jong.choi at intel.com>>:
Hi Mr. Kim,

May confirm which environment are you using?
x86_64-default-linuxapp-gcc or
x86_64-native-linuxapp-gcc




Regards,
Choi, Sy Jong

-Original Message-
From: BYEONG-GI KIM [kimbyeonggi at gmail.com]
Sent: Monday, July 14, 2014 10:05 AM Malay Peninsula Standard Time
To: Masaru Oki; dev at dpdk.org; Dpdk-ovs at 
lists.01.org
Subject: Re: [dpdk-dev] Error while compiling DPDK

Here is the error message in English;

== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/igb_uio
  LD
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
  CC [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
  LD [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
INSTALL-MODULE igb_uio.ko
== Build lib/librte_eal/linuxapp/eal
  CC eal.o
gcc: error: ?g: No such file or directory
make[7]: *** [eal.o] Error 1
make[6]: *** [eal] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [x86_64-default-linuxapp-gcc_install] Error 2
make: *** [install] Error 2



2014-07-14 11:02 GMT+09:00 Masaru Oki mailto:m-oki 
at stratosphere.co.jp>>:

> > I'm sorry for the Korean characteristics. It was shown because My Fedora
> OS
> > is set to use Korean as a default language.
>
> Try env LANG=C make install ...
>
>
> 2014-07-14 10:24 GMT+09:00 BYEONG-GI KIM  gmail.com>:
>
>> Dear choi,
>>
>> Thank you for the reply.
>>
>> I've been trying to install DPDK while changing the command as you
>> mentioned, i.e., I used T=x86_64-default-linuxapp-gcc, but error was still
>> shown;
>>
>>
>> [root at compute DPDK-1.6.0]# make install T=x86_64-default-linuxapp-gcc
>> == Installing x86_64-default-linuxapp-gcc
>> Configuration done
>> == Build scripts
>> == Build scripts/testhost
>>   HOSTCC testhost.o
>>   HOSTLD testhost
>>   INSTALL-HOSTAPP testhost
>> == Build lib
>> == Build lib/librte_eal
>> == Build lib/librte_eal/common
>>   SYMLINK-FILE include/rte_atomic.h
>>   SYMLINK-FILE include/rte_branch_prediction.h
>>   SYMLINK-FILE include/rte_byteorder.h
>>   SYMLINK-FILE include/rte_common.h
>>   SYMLINK-FILE include/rte_cycles.h
>>   SYMLINK-FILE include/rte_debug.h
>>   SYMLINK-FILE include/rte_eal.h
>>   SYMLINK-FILE include/rte_errno.h
>>   SYMLINK-FILE include/rte_launch.h
>>   SYMLINK-FILE include/rte_lcore.h
>>   SYMLINK-FILE include/rte_log.h
>>   SYMLINK-FILE include/rte_memcpy.h
>>   SYMLINK-FILE include/rte_memory.h
>>   SYMLINK-FILE include/rte_memzone.h
>>   SYMLINK-FILE include/rte_pci.h
>>   SYMLINK-FILE include/rte_pci_dev_ids.h
>>   SYMLINK-FILE include/rte_per_lcore.h
>>   SYMLINK-FILE include/rte_prefetch.h
>>   SYMLINK-FILE include/rte_random.h
>>   SYMLINK-FILE include/rte_rwlock.h
>>   SYMLINK-FILE include/rte_spinlock.h
>>   SYMLINK-FILE include/rte_tailq.h
>>   SYMLINK-FILE include/rte_interrupts.h
>>   SYMLINK-FILE include/rte_alarm.h
>>   SYMLINK-FILE include/rte_string_fns.h
>>   SYMLINK-FILE include/rte_cpuflags.h
>>   SYMLINK-FILE include/rte_version.h
>>   SYMLINK-FILE include/rte_tailq_elem.h
>>   SYMLINK-FILE include/rte_eal_memconfig.h
>>   SYMLINK-FILE include/rte_malloc_heap.h
>>   SYMLINK-FILE include/rte_hexdump.h
>>   SYMLINK-FILE include/arch/rte_atomic.h
>> == Build lib/librte_eal/linuxapp
>> == Build lib/librte_eal/linuxapp/igb_uio
>>   LD
>>
>>  
>> 

[dpdk-dev] Error while compiling DPDK

[Choi, Sy Jong]

Hi Mr. Kim,

May confirm which environment are you using?
x86_64-default-linuxapp-gcc or
x86_64-native-linuxapp-gcc



Regards,
Choi, Sy Jong

-Original Message-
From: BYEONG-GI KIM [kimbyeonggi at gmail.com]
Sent: Monday, July 14, 2014 10:05 AM Malay Peninsula Standard Time
To: Masaru Oki; dev at dpdk.org; Dpdk-ovs at lists.01.org
Subject: Re: [dpdk-dev] Error while compiling DPDK


Here is the error message in English;

== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/igb_uio
  LD
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
  CC [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
  LD [M]
 
/home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
INSTALL-MODULE igb_uio.ko
== Build lib/librte_eal/linuxapp/eal
  CC eal.o
gcc: error: ?g: No such file or directory
make[7]: *** [eal.o] Error 1
make[6]: *** [eal] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [x86_64-default-linuxapp-gcc_install] Error 2
make: *** [install] Error 2



2014-07-14 11:02 GMT+09:00 Masaru Oki :

> > I'm sorry for the Korean characteristics. It was shown because My Fedora
> OS
> > is set to use Korean as a default language.
>
> Try env LANG=C make install ...
>
>
> 2014-07-14 10:24 GMT+09:00 BYEONG-GI KIM :
>
>> Dear choi,
>>
>> Thank you for the reply.
>>
>> I've been trying to install DPDK while changing the command as you
>> mentioned, i.e., I used T=x86_64-default-linuxapp-gcc, but error was still
>> shown;
>>
>>
>> [root at compute DPDK-1.6.0]# make install T=x86_64-default-linuxapp-gcc
>> == Installing x86_64-default-linuxapp-gcc
>> Configuration done
>> == Build scripts
>> == Build scripts/testhost
>>   HOSTCC testhost.o
>>   HOSTLD testhost
>>   INSTALL-HOSTAPP testhost
>> == Build lib
>> == Build lib/librte_eal
>> == Build lib/librte_eal/common
>>   SYMLINK-FILE include/rte_atomic.h
>>   SYMLINK-FILE include/rte_branch_prediction.h
>>   SYMLINK-FILE include/rte_byteorder.h
>>   SYMLINK-FILE include/rte_common.h
>>   SYMLINK-FILE include/rte_cycles.h
>>   SYMLINK-FILE include/rte_debug.h
>>   SYMLINK-FILE include/rte_eal.h
>>   SYMLINK-FILE include/rte_errno.h
>>   SYMLINK-FILE include/rte_launch.h
>>   SYMLINK-FILE include/rte_lcore.h
>>   SYMLINK-FILE include/rte_log.h
>>   SYMLINK-FILE include/rte_memcpy.h
>>   SYMLINK-FILE include/rte_memory.h
>>   SYMLINK-FILE include/rte_memzone.h
>>   SYMLINK-FILE include/rte_pci.h
>>   SYMLINK-FILE include/rte_pci_dev_ids.h
>>   SYMLINK-FILE include/rte_per_lcore.h
>>   SYMLINK-FILE include/rte_prefetch.h
>>   SYMLINK-FILE include/rte_random.h
>>   SYMLINK-FILE include/rte_rwlock.h
>>   SYMLINK-FILE include/rte_spinlock.h
>>   SYMLINK-FILE include/rte_tailq.h
>>   SYMLINK-FILE include/rte_interrupts.h
>>   SYMLINK-FILE include/rte_alarm.h
>>   SYMLINK-FILE include/rte_string_fns.h
>>   SYMLINK-FILE include/rte_cpuflags.h
>>   SYMLINK-FILE include/rte_version.h
>>   SYMLINK-FILE include/rte_tailq_elem.h
>>   SYMLINK-FILE include/rte_eal_memconfig.h
>>   SYMLINK-FILE include/rte_malloc_heap.h
>>   SYMLINK-FILE include/rte_hexdump.h
>>   SYMLINK-FILE include/arch/rte_atomic.h
>> == Build lib/librte_eal/linuxapp
>> == Build lib/librte_eal/linuxapp/igb_uio
>>   LD
>>
>>  
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/built-in.o
>>   CC [M]
>>
>>  
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.o
>>   Building modules, stage 2.
>>   MODPOST 1 modules
>>   CC
>>
>>  
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.mod.o
>>   LD [M]
>>
>>  
>> /home/stack/dpdk/DPDK-1.6.0/x86_64-default-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.ko
>> INSTALL-MODULE igb_uio.ko
>> == Build lib/librte_eal/linuxapp/eal
>>   CC eal.o
>> gcc: error: ?g: ??  ? 
>> make[7]: *** [eal.o] ?? 1
>> make[6]: *** [eal] ?? 2
>> make[5]: *** [linuxapp] ?? 2
>> make[4]: *** [librte_eal] ?? 2
>> make[3]: *** [lib] ?? 2
>> make[2]: *** [all] ?? 2
>> make[1]: *** [x86_64-default-linuxapp-gcc_install] ?? 2
>> make: *** [install] ?? 2
>>
>> I'm sorry for the Korean characteristics. It was shown because My Fedora
>> OS
>> is set to use Korean as a default language.
>>
>> I set two environmental variables following the
>> intel-dpdk-programmers-guide.pdf as below:
>>
>> export RTE_SDK=/home/stack/dpdk/DPDK-1.6.0
>> export RTE_TARGET=x86_64-native-linuxapp-gcc
>>
>> What should I do in order to install DPDK successfully?...
>>
>> Thanks in advance.
>>

[dpdk-dev] Error while compiling DPDK

[Choi, Sy Jong]

Hi Mr. Kim,

Please do not compile with "T=x86*gcc" because it will compile BSD app too, 
which cause the error.

Please complile only the configuration you need. This should remove the error.


Regards,
Choi, Sy Jong

-Original Message-
From: BYEONG-GI KIM [kimbyeonggi at gmail.com]
Sent: Monday, July 14, 2014 08:25 AM Malay Peninsula Standard Time
To: Dpdk-ovs at lists.01.org; dev at dpdk.org
Subject: [dpdk-dev] Error while compiling DPDK


Hello.

An error occured while compiling DPDK 1.6.0r2 as below:

[root at compute dpdk-1.6.0r2]# make install T=x86_64*gcc
...Installing...
/ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c: In function
?rte_eal_init?:
/ovdk/dpdk/dpdk-1.6.0r2/lib/librte_eal/bsdapp/eal/eal.c:873:2: error:
format ?%p? expects argument of type ?void *?, but argument 5 has type
?pthread_t? [-Werror=format=]
  RTE_LOG(DEBUG, EAL, "Master core %u is ready (tid=%p)\n",
  ^

The current OS is Fedora20. What should I do?...

Best regards

Byeong-Gi KIM