Hi Saurabh,
I don't know all the details of your setup, but I'm guessing that you may
have run into the hugepage fragmentation issue.
Try calling rte_malloc_dump_stats(stdout, "dummy") right before the mempool
creation. Output might look like this:
Socket:0
Heap_size:2147472192,
Free_size:20475
So you mean,
each core works with its thread as a worker, and in the ring as a share
memory, all cores(via their threads) could write and read in each part of
the ring (but it is better each core access to its threads).
My questions:
1) How I could access to cache/register/etc of each core if so?
2
On 03/11/2016 08:46 PM, Douglas, Frederick E wrote:
> I'm new to DPDK. I've gotten the basics working, but I'm having trouble with
> the .pcap file-based virtual interface. The EAL is failing to set things up
> when I ask it to use a pcap virtual interface, with:
>
> --vdev
> 'eth_pcap0,rx_pcap=
Hi,
We are planning to support virtio, vmxnet3, ixgbe, i40e, bxn2x and SR-IOV
on some of them with DPDK.
We have seen that even if we give correct number of mbufs given the number
hugepages reserved, rte_eth_tx_queue_setup() may still fail with no enough
memory (I saw this on i40evf but worked on
I have tried everything from 400 to 777 (rwx permissions on the config
file) on the host (which gets reflected in the container as well), but
still EAL complains it cannot open the file. Any ideas/workarounds for
this issue, please?. If I do it from the host, it works fine..
--
EAL: Cannot open /s