From: "Alan.Birtles@sony.com" <Alan.Birtles@sony.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Connectx-6 LX scheduled sending only sending 25 packets
Date: Tue, 8 Feb 2022 09:33:33 +0000 [thread overview]
Message-ID: <AS8P193MB1734386BCC2CED4DF59BBA94E52D9@AS8P193MB1734.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AS8P193MB1734D1E3291AE4A0BDCA9AA6E52C9@AS8P193MB1734.EURP193.PROD.OUTLOOK.COM>
[-- 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 --]
next prev parent reply other threads:[~2022-02-08 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 17:45 Alan.Birtles
2022-02-08 9:33 ` Alan.Birtles [this message]
2022-02-08 15:15 ` Alan.Birtles
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AS8P193MB1734386BCC2CED4DF59BBA94E52D9@AS8P193MB1734.EURP193.PROD.OUTLOOK.COM \
--to=alan.birtles@sony.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).