The latest developments, news, releases, events and highlights from the global
DPDK community.
View in browser
(https://email.linuxfoundation.org/e3t/Ctc/RI+113/cZw--04/VWBP8Z97SzMnW23V82h3Cy0kzW50jS
Hello.
Thanks a lot in advance for your help and nice support.
We use tap PMD to send exception packet to kernel by DPDK primary block.
If the secondary block is driven in this state, vdev probe is
performed inside rte_eal_init
func
and memory is allocated using the rte_zmalloc_socket function if
Hi. I am using Intel (i210) and AWS ENA network interface cards.
I would like to measure the following RX latencies:
1) NIC to DPDK packet ring buffer
2) DPDK packet ring buffer to application via rte_eth_rx_burst.
I don't mind measuring in nanoseconds or CPU cycles.
Unfortunately I c
I was looking at the source code but I'm more OOP C++ than C. I found
eth_ena_recv_pkts but is it possible for me to add a software
timestamp before the mbuf is added to the ring buffer? This would be
incredibly useful.
On Mon, 9 Sept 2024 at 09:31, Brandes, Shai wrote:
>
>
> >
From: NSWE SWS DPDK Dev
i225 devices have only one PHY vendor. There is unnecessary to check _I_PHY_ID
during the link establishment
and auto-negotiation process, the checking also caused devices like i225-IT
failed. This patch is to remove the
mentioned unnecessary checking.
Cc: sta
From: NSWE SWS DPDK Dev
i225 devices have only one PHY vendor. There is unnecessary to check
_I_PHY_ID during the link establishment and auto-negotiation process,
the checking also caused devices like i225-IT failed. This patch is to
remove the mentioned unnecessary checking.
Cc: sta
7 matches
Mail list logo
