Hi
I downloaded DPDK 1.6 from the Intel website and ran into couple of
compilation errors with /lib/librte_eal/linuxapp/eal/eal_ivshmem.c. The
following changes seem to fix it. Have other people seen these?
Thanks
Jyoti
@@ -472,7 +472,7 @@
rte_snprintf(path, sizeof(path), IVSHMEM_CONFIG_PATH
Hi
The rte_mempool and rte_ring libs have multi-producer/multi-consumer
versions. But it's also mentioned in the header files that the
implementation is not pre-emtable : " Note: the mempool implementation is
not preemptable. A lcore must not be interrupted by another task that uses
the same mempo
Hi Romulo
You can check lib/librte_eal/common/include/rte_pci_dev_ids.h for supported
NICs.
Also from your pci_unbind status , does not look like any NIC is bound to
igb_uio..
On Sat, Dec 14, 2013 at 9:24 PM, Romulo Rosa wrote:
> Thanks Paul,
>
> But i think my NICS are not supportted by Intel
, 2013 at 8:32 PM, Romulo Rosa wrote:
> Thanks for the feedback. I compiled the DPDK with the -fPIC option. Is
> there any specific location in the Makefile DPDK where should I put the
> -fPIC option?
>
>
> 2013/12/7 Jyotiswarup Raiturkar
>
>> You need to compile DPDK with
You need to compile DPDK with -fPIC option..
-Jyoti
On Sat, Dec 7, 2013 at 5:50 PM, Romulo Rosa wrote:
> Hi,
>
> I'm trying to compile QEMU on Ubuntu 12:04 and'm having the following
> problem:
>
> LINK x86_64-softmmu/qemu-system-x86_64
> /usr/bin/ld:
>
> /home/xerifao/ovs_dpdk/dpdk-1.5.1r1/x
This should fix it
diff --git a/openvswitch/Makefile.am b/openvswitch/Makefile.am
index fbee87b..b8da768 100644
--- a/openvswitch/Makefile.am
+++ b/openvswitch/Makefile.am
@@ -28,7 +28,9 @@ endif
@HAVE_DPDK_TRUE@$(dpdk_lib_dir)/librte_mbuf.a \
@HAVE_DPDK_TRUE@$(dpdk_lib_dir)/librte_r
ts before
> > (rte_eal_init(), rte_pmd_init_all() and don't forget
> rte_eal_pci_probe())?
> >
> > Regards,
> > Daniel
> >
> >
> > On Wed, Nov 13, 2013 at 1:27 PM, Jose Gavine Cueto > >wrote:
> >
> > > Hi,
> > >
> > > How
On Tue, Nov 5, 2013 at 9:34 PM, Cyril Cressent wrote:
> On Tue, Nov 05, 2013 at 08:01:06PM +0530, Jyotiswarup Raiturkar wrote:
>
> > Thanks for the quick reply. I saw some definitions of e1000_phy_82579
> hence
> > I thought (hoped) the NIC would be supported. I will try to run
Tue, Nov 05, 2013 at 05:41:17PM +0530, Jyotiswarup Raiturkar wrote:
> >
> > I have 82579LM NIC which i'm trying to bind to the igb_uio driver. I get
> > the following error
>
> I can't find the 82579LM listed on
> http://dpdk.org/doc/nics
> or in
> lib/libr
Hello
I'm trying to install DPDK on my laptop.
I have 82579LM NIC which i'm trying to bind to the igb_uio driver. I get
the following error
# ./tools/pci_unbind.py --status
Network devices using IGB_UIO driver
Network devices using kernel driver
==
t; Regards
> -Prashant
>
>
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jyotiswarup Raiturkar
> Sent: Wednesday, October 23, 2013 5:10 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] query about port queues
>
> Hello Devs
> I
nal Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jyotiswarup Raiturkar
> Sent: Wednesday, October 23, 2013 5:11 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] query about rte_eal_mp_remote_launch()
>
> Hello Devs
> I'm new to DPDK and trying to under
Can I use pthread_create() on-the-fly (taking
care of CPU core allocation), after doing an initial threads launch using
rte_eal_mp_remote_launch()?
Thanks
Jyotiswarup Raiturkar
l the queues
on the port? (and hence will an application like say a network stack need
packets from all the queues in the port)?
Thanks
Jyotiswarup Raiturkar
14 matches
Mail list logo
