What's the advantage of DPDK over another accelaration framework called netmap?
Well done!
I guess that's the shortest question on the list, and probably the one
that's going to trigger the largest discussion.
A few months, ago I had to answer it for a customer. And here is my
understanding:
- DPDK is also a high performance multi-core application framework. You take
out t
Hi Srini,
Thanks, I could also make it work, thanks to your cue !
Now then, this multi-segment not being supported in vmxnet3 driver is a big
party-pooper for me. Unfortunately in my usecase, I do indeed make heavy use of
multisegment buffers for sending out the data, so my usecase has failed a
Hi,
Regarding performance with vmxnet3 driver, the programmer's guide says thus --
"
Currently, the driver provides basic support for using the device in an
Intel(r) DPDK
application running on a guest OS. Optimization is needed on the backend, that
is, the
VMware* ESXi vmkernel switch, to achi
Can anyone help me resolve this issue? We have bought the 82571EB dual port NIC
and we are not able to run the DPDK pmd userapp on it.
Please update if there is any issue.
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Chetan Bali
Sent: 09 March 2014 19:49
To: St
On Mon, 10 Mar 2014 13:30:48 +0530
Prashant Upadhyaya wrote:
> Hi Srini,
>
> Thanks, I could also make it work, thanks to your cue !
>
> Now then, this multi-segment not being supported in vmxnet3 driver is a big
> party-pooper for me. Unfortunately in my usecase, I do indeed make heavy use
>
This is talk I did a couple of years ago.
http://www.slideshare.net/shemminger/uio-final
I also got the segfault. Setting CONFIG_RTE_EAL_UNBIND_PORTS=y is not ideal
because it would also unbind my VMNET3 management interface.
Does anyone know why the crash is happening? According to the stacktrace,
hw_addrX is 0x0 during eth_vmxnet3_dev_init.
I?m running on ubuntu 12.04LTS on ESXi
Upon further trace, I know what caused it. The uio hardware resources were
never memory mapped when RTE_EAL_UNBIND_PORTS is not enabled. Specifically,
pci_dev->mem_resource[] is not mapped. This explains why setting
CONFIG_RTE_EAL_UNBIND_PORTS=y fixes the problem.
lib/librte_pmd_vmxnet3/vmxne
virtio-pmd has the same pattern. I wonder if vmxnet3-pmd just blindly copied
the same paradigm.
lib/librte_pmd_virtio/virtio_ethdev.c
473 static struct eth_driver rte_virtio_pmd = {
474 {
475 .name = "rte_virtio_pmd",
476 .id_table = pci_id_virtio_map,
477 #ifdef RTE_EAL_UNBI
10 matches
Mail list logo
