DPDK usage discussions
 help / color / mirror / Atom feed
* Connectx-6 LX scheduled sending only sending 25 packets
@ 2022-02-07 17:45 Alan.Birtles
  2022-02-08  9:33 ` Alan.Birtles
  0 siblings, 1 reply; 3+ messages in thread
From: Alan.Birtles @ 2022-02-07 17:45 UTC (permalink / raw)
  To: users

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

We are trying to use send scheduling on a Connectx-6 LX. If we set no timestamps on the packet buffers and manually send each packet at approximately the right time everything works. However if we set timestamps in the buffers then the first 25 packets are sent and the packets are received at the expected times but all subsequent calls to rte_eth_tx_burst return 0. If its relevant we are sending a single packet in each burst with timestamps 125 us apart.
We've tried setting the timestamps to low values and the packets are transmitted correctly and as expected the tx_pp_timestamp_past_errors value is incremented. We also set high values and this worked too with tx_pp_timestamp_future_errors incrementing.
Any ideas where to start debugging this? I couldn't see any API which would give an error code for rte_eth_tx_burst failing.
We're using DPDK 21.08 with the 5.4.3.1 mellanox driver on ubuntu 20.04.

[-- Attachment #2: Type: text/html, Size: 2555 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Connectx-6 LX scheduled sending only sending 25 packets
  2022-02-07 17:45 Connectx-6 LX scheduled sending only sending 25 packets Alan.Birtles
@ 2022-02-08  9:33 ` Alan.Birtles
  2022-02-08 15:15   ` Alan.Birtles
  0 siblings, 1 reply; 3+ messages in thread
From: Alan.Birtles @ 2022-02-08  9:33 UTC (permalink / raw)
  To: users

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

We are trying to use send scheduling on a Connectx-6 LX. If we set no timestamps on the packet buffers and manually send each packet at approximately the right time everything works. However if we set timestamps in the buffers then the first 25 packets are sent and the packets are received at the expected times but all subsequent calls to rte_eth_tx_burst return 0. If its relevant we are sending a single packet in each burst with timestamps 125 us apart.
We've tried setting the timestamps to low values and the packets are transmitted correctly and as expected the tx_pp_timestamp_past_errors value is incremented. We also set high values and this worked too with tx_pp_timestamp_future_errors incrementing.
Any ideas where to start debugging this? I couldn't see any API which would give an error code for rte_eth_tx_burst failing.
We're using DPDK 21.08 with the 5.4.3.1 mellanox driver on ubuntu 20.04.

[-- Attachment #2: Type: text/html, Size: 2397 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: Connectx-6 LX scheduled sending only sending 25 packets
  2022-02-08  9:33 ` Alan.Birtles
@ 2022-02-08 15:15   ` Alan.Birtles
  0 siblings, 0 replies; 3+ messages in thread
From: Alan.Birtles @ 2022-02-08 15:15 UTC (permalink / raw)
  To: users

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

It looks like this was caused by not having enough TX descriptors, we were only specifying 64, increasing to 1024 fixes the problem.

From: Birtles, Alan
Sent: 08 February 2022 09:34
To: users@dpdk.org
Subject: Connectx-6 LX scheduled sending only sending 25 packets

We are trying to use send scheduling on a Connectx-6 LX. If we set no timestamps on the packet buffers and manually send each packet at approximately the right time everything works. However if we set timestamps in the buffers then the first 25 packets are sent and the packets are received at the expected times but all subsequent calls to rte_eth_tx_burst return 0. If its relevant we are sending a single packet in each burst with timestamps 125 us apart.
We've tried setting the timestamps to low values and the packets are transmitted correctly and as expected the tx_pp_timestamp_past_errors value is incremented. We also set high values and this worked too with tx_pp_timestamp_future_errors incrementing.
Any ideas where to start debugging this? I couldn't see any API which would give an error code for rte_eth_tx_burst failing.
We're using DPDK 21.08 with the 5.4.3.1 mellanox driver on ubuntu 20.04.

[-- Attachment #2: Type: text/html, Size: 3209 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-02-10  9:13 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-07 17:45 Connectx-6 LX scheduled sending only sending 25 packets Alan.Birtles
2022-02-08  9:33 ` Alan.Birtles
2022-02-08 15:15   ` Alan.Birtles

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).