DPDK usage discussions
 help / color / mirror / Atom feed
From: madhukar mythri <madhukar.mythri@gmail.com>
To: Nishant Verma <vnish11@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: i40e PMD: Tx hang issue
Date: Sat, 20 May 2023 12:36:20 +0530	[thread overview]
Message-ID: <CAAUNki035dQYUXw1aM7Kfy66ZOR6M-OWOLwjeK-A=XcQ9zLrPA@mail.gmail.com> (raw)
In-Reply-To: <CAHhCjUFwG=y-PHxQJcKo=gSk-KRorcOVzwcrAR96Xyx2703xRA@mail.gmail.com>

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

Hi Nishant,

Our application runs on top of DPDK-21.11 with net_i40e PMD(X710 NIC).
After running traffic for some days(8 to 10 days), intermittently we could
see Tx-shall on Queue-0(we had enabled only a single queue) and this was
identified by looking into the Rx/Tx eth-stats of NIC, where we could see
Tx-packets stats was not incremented and only Rx-stats were incremented and
the 'rte_eth_tx_burst()', this function returns '0'.

Work-arounds: Monitor this Rx/Tx stats for every second in an other thread
and do the following steps:
1) Restart the PMD. using rte_eth_dev_stop(port) , usleep(10) and
rte_eth_dev_start().
2) Restart the respective Tx Queue-0 only, which got stalled, by
using rte_eth_dev_tx_queue_stop() and rte_eth_dev_tx_queue_start().

First approach takes a long time(around 10 seconds) to recover the NIC.
whereas the second approach recovers within < 3 seconds.

Regards,
Madhukar.


On Thu, May 18, 2023 at 5:34 PM Nishant Verma <vnish11@gmail.com> wrote:

> Hi Madhukar,
>
> Can you please elaborate what issue you found in TX-side? Any solution for
> that?
> For me it seems to be both rx and tx.
>
>
> Thanks.
>
> Regards,
> Nishant Verma
>
>
> On Mon, May 8, 2023 at 2:53 AM madhukar mythri <madhukar.mythri@gmail.com>
> wrote:
>
>> Hi,
>>
>> We are facing an issue at the Transmit side randomly after 8 to 10 days
>> of network traffic flow on the Intel X710 10G NIC with i40e PMD.
>> We found the issue is at Transmit side Tx-queue, as the Tx packets were
>> not going out and also observed that the Tx-queue stats were not
>> incrementing, even though we are sending packets out through the
>> 'rte_eth_tx_burst()', this function returns '0'. Whereas the Rx-packets
>> were received well at the same-time and Rx-stats were incremented well,
>> even the NIC Link is also stable at 1G speed.
>>
>> So, has anyone faced such issue on this DPDK i40e PMD at Transmit
>> side(Tx-queue), if so, please let us know, if any known-issue 'Or'
>> fix/work-around on this.
>>
>> DPDK-version: DPDK-21.11
>> X710 NIC speed: Connected with 1G speed switch-port. so, as per
>> auto-negotiation the link-speed is 1G only.
>> X710 NIC firmware-version: "fw 6.0.48442 api 1.7 nvm 6.01 0x80003b43
>> 1.1824.0 [8086:1589] [108e:7b1c]".
>>
>> Thanks,
>> Madhukar.
>>
>

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

      reply	other threads:[~2023-05-20  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  6:52 madhukar mythri
2023-05-18 12:04 ` Nishant Verma
2023-05-20  7:06   ` madhukar mythri [this message]

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='CAAUNki035dQYUXw1aM7Kfy66ZOR6M-OWOLwjeK-A=XcQ9zLrPA@mail.gmail.com' \
    --to=madhukar.mythri@gmail.com \
    --cc=users@dpdk.org \
    --cc=vnish11@gmail.com \
    /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).