DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Rajasekhar Pulluru <pullururajasekhar@gmail.com>
Cc: dev@dpdk.org
Subject: Re: Multiple Tx-Queues not working as expected
Date: Fri, 17 Feb 2023 08:26:50 -0800	[thread overview]
Message-ID: <20230217082650.1968dcd8@hermes.local> (raw)
In-Reply-To: <CAGA5_H6kg-6tZozY5hKL8sFBJNrKGd2kTxAdDXitUGcHcFuA6w@mail.gmail.com>

On Fri, 17 Feb 2023 11:30:14 +0530
Rajasekhar Pulluru <pullururajasekhar@gmail.com> wrote:

> Ok Stephen, thanks for the information, I can try that.
> 
> One of the problems I see with single Tx Queue mode is that Ixia reports
> packet drops, though I confirmed with the help of counters (before invoking
> tx burst) that all packets are being sent-out. Dumping HW counters don't
> report any drops in TX.
> Is there a mechanism in DPDK to debug this?
> 
> Thanks & Regards,
> Rajasekhar

The common usage in DPDK is to have one transmit queue per DPDK thread doing
transmits.  If the transmit queue is not configured with enough depth.

The most common packet flow in DPDK is packets getting received, modified
then transmitted. With that pattern, packet loss is at the receiver when
the CPU can't keep up with the packet rate arriving.

  reply	other threads:[~2023-02-17 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 18:10 Rajasekhar Pulluru
2023-02-16 19:51 ` Stephen Hemminger
2023-02-17  6:00   ` Rajasekhar Pulluru
2023-02-17 16:26     ` Stephen Hemminger [this message]
2023-02-17 17:33       ` Rajasekhar Pulluru
2023-02-17 16:38     ` Bruce Richardson
2023-02-17 17:38       ` Rajasekhar Pulluru

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=20230217082650.1968dcd8@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=pullururajasekhar@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).