Hi, Yan
Sorry, I do not follow the letter?
Are you proposing the patch for bonding PMD?
If so, could you, please send your patch in plain text, according to ML rules?
It is application responsibility to start bonding virtual device (and it will
start its slaves)
before flow creation.
With
Hi, team
We have the problem of running the dpdk-l3fwd application inside a VM.
The tool can’t be started inside the VM with the following error message:
dpdk-l3fwd -l 1 -- -p 0x3 --config="(0,0,1),(1,0,1)" --parse-ptype
EAL: Detected CPU lcores: 9
EAL: Detected NUMA nodes: 1
EAL:
Hello,
The first error is "Cause: Error: number of ports must be even"
03/05/2023 18:13, Igor de Paula:
> I am running a VM inside a VMWARE server (vSphere).
> My goal it to set up DPDK with two HW ports, and set up a virtio_user to
> interact with the kernel stack.
> In another app I have it
Answer my own question for future google searches.
Digging through the mlx5 driver source, it looks through the netlink
kernel interface to get details about the hardware. Without access to
the kernel data, DPDK can't init the mlx5 driver.
You need to pass the interface into the container
> From: Hari Haran
> Sent: Wednesday, July 19, 2023 4:30 PM
> To: Van Haaren, Harry
> Cc: users@dpdk.org
> Subject: Re: Inflight value shown invalid in Event Dev Queue
>
> Hi Harry Haaren (Yes :) )
>
> I have given more details below, please check this.
Please reply "in-line", it makes it
Hi Harry Haaren (Yes :) )
I have given more details below, please check this.
*Device Configuration:*
Event Dev Queue : 1
Number of ports : 3
Queue 0 depth - 32k
Port 0, 1 amd 2 : Enqueue depth 4096, Dequeue depth 128
*Cores: *
Rx core - 1
Workers cores - 2
*Port 2:*
Used in Rx core - Used to
> From: Hari Haran
> Sent: Wednesday, July 19, 2023 1:39 PM
> To: users@dpdk.org
> Subject: Inflight value shown invalid in Event Dev Queue
>
> Hi All,
Hi Hari Haran,
> Once packets dequeued from port 0, still inflight stats shown same as
> dequeued count.
> After that, enqueue failure
Hi All,
Once packets dequeued from port 0, still inflight stats shown same as
dequeued count.
After that, enqueue failure happens for port 2 from another core due to it
reaches Max Enqueue depth .
*Port 0 Stats:*
Below case, port 0 dequeued 4096 packets and still inflight showed the same
value.
Hello,
I'm trying to use the flow-filtering sample application in DPDK v22.03. The
code runs well with Intel X520 NICs, in the sense that packets with
192.168.1.1 as destination IP are sent to queue #1.
The very same code with Intel XL710 does not work; packets are all sent to
queue #0 regardless
