DPDK patches and discussions
 help / color / mirror / Atom feed
From: RajeshKumar Kalidass <rajesh.kalidass@gigamon.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Rakesh Jagota <rakesh.jagota@gigamon.com>,
	Tanmay Kishore <tanmay.kishore@gigamon.com>,
	Hung Nguyen <hung.nguyen@gigamon.com>
Subject: [dpdk-dev] net/mlx5: no TX in multi-process setup (testpmd working)
Date: Mon, 19 Apr 2021 13:33:45 +0000	[thread overview]
Message-ID: <BY5PR12MB3745D4F18D495529E1B78EE8F2499@BY5PR12MB3745.namprd12.prod.outlook.com> (raw)

Hi,

DPDK: 19.11
OS: Ubuntu 18.04 (Kernel: 5.4.0-1043-azure)
Iface: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function]

We are bringing-up our dpdk based app on azure cloud, its multi-process setup (primary does dev_configure & dev_start ) - however no packet are getting transmitted out (Tx-packet increases upto number of descriptor and then all further packets are txDropped)

"stats": [
    {
      "name": "rep1",
      "txPkts": 1024,           <<<<<<----------------------- it increases upto number of tx-descriptors
      "rxPkts": 5408,
      "txBytes": 65536,
      "rxBytes": 346112,
      "txDropped": 4384,  <<<<<<--------------------- All further packets are txDropped
      "rxDropped": 96,
      "txErrors": 0,
      "rxErrors": 0
    }
  ]

However mlx4 driver is working perfectly fine on multi-process setup. Also testpmd working fine with mlx5. I guess problem is when we try to run in multi-process setup ?


Thanks,
-Rajesh

This message may contain confidential and privileged information. If it has been sent to you in error, please reply to advise the sender of the error and then immediately delete it. If you are not the intended recipient, do not read, copy, disclose or otherwise use this message. The sender disclaims any liability for such unauthorized use. NOTE that all incoming emails sent to Gigamon email accounts will be archived and may be scanned by us and/or by external service providers to detect and prevent threats to our systems, investigate illegal or inappropriate behavior, and/or eliminate unsolicited promotional emails ("spam").

             reply	other threads:[~2021-04-20  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 13:33 RajeshKumar Kalidass [this message]
2021-04-19 13:35 Rajesh Kumar
2021-04-20 11:16 ` Rajesh Kumar
2021-04-20 14:51   ` Tanmay Kishore

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=BY5PR12MB3745D4F18D495529E1B78EE8F2499@BY5PR12MB3745.namprd12.prod.outlook.com \
    --to=rajesh.kalidass@gigamon.com \
    --cc=dev@dpdk.org \
    --cc=hung.nguyen@gigamon.com \
    --cc=rakesh.jagota@gigamon.com \
    --cc=tanmay.kishore@gigamon.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).