DPDK usage discussions
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: benli ye <danielbenliye@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>, Ori Kam <orika@mellanox.com>,
	Dekel Peled <dekelp@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-users] net/mlx5 statistics related
Date: Fri, 2 Aug 2019 21:53:05 +0000	[thread overview]
Message-ID: <C5F9E43B-484A-4D1E-9254-37C00E37EF71@mellanox.com> (raw)
In-Reply-To: <3A12285D-775A-4DEC-98C9-20711054F4D7@gmail.com>

Hi,

Can you try the following patch, which had been added after 18.11.0
I'll try to push it for 18.11.3.

http://git.dpdk.org/dpdk/commit/?id=ce9494d76c478345679abbda2a5606646de9886f


Thanks,
Yongseok

> On Jul 28, 2019, at 2:12 AM, benli ye <danielbenliye@gmail.com> wrote:
> 
> Dear Mellanox experts,
> 
> I am running DPDK 18.11.0 performance test with mlx5 PMD driver on device ConnectX®-4 Lx EN. Our own DPDK app (a Load Balance app) is used and UDP 64 bytes is generated by tester.
> We found that when we generated about 2.6Mpps UDP traffic for 1 core and 2 port setting testbed, our app starts to drops packets. However, the strange issue is we cannot see any imissed or error statistics from DPDK layer.
> I saw the Mellanox test performance result in https://fast.dpdk.org/doc/perf/DPDK_18_11_Mellanox_NIC_performance_report.pdf and how do you find packet lose? Is there a bug in statistic calculation in DPDK or there is another way to trace packet drop?
> Retrieve DPDK statistics is also used for Intel NIC and the behavior is right. it should not be wrong for our usage in our own app.
> 
> Any suggestions would be welcomed. Thanks very much!
> 
> 
> Bests,
> Daniel Benli Ye


  reply	other threads:[~2019-08-02 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28  9:12 benli ye
2019-08-02 21:53 ` Yongseok Koh [this message]
2019-08-05  2:30   ` benli ye
2019-10-24  3:05     ` [dpdk-users] Fwd: " benli ye

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=C5F9E43B-484A-4D1E-9254-37C00E37EF71@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=danielbenliye@gmail.com \
    --cc=dekelp@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=users@dpdk.org \
    --cc=viacheslavo@mellanox.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).