DPDK usage discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Arjun Roy <arroy@eng.ucsd.edu>
Cc: Shahaf Shuler <shahafs@mellanox.com>,
	Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Mellanox ConnectX-4, DPDK and extreme latency issues
Date: Mon, 4 Sep 2017 17:52:52 +0200	[thread overview]
Message-ID: <20170904155252.GZ4301@6wind.com> (raw)
In-Reply-To: <VI1PR05MB3149F11F671A477F2CA7254BC3D20@VI1PR05MB3149.eurprd05.prod.outlook.com>

Arjun,

On Thu, Jun 29, 2017 at 05:26:02AM +0000, Shahaf Shuler wrote:
> Hi Arjun,
> 
> Thursday, June 22, 2017 9:40 PM, Arjun Roy,
> > 
> > Greetings all.
> > 
> > I have a weird issue regarding excessive latency using Mellanox ConnectX-4
> > 100Gbe cards, DPDK and packet forwarding. Specifically: running the l3fwd
> > and basicfwd DPDK example programs yields ping latencies of several (5-8)
> > milliseconds. I tried the same test using an Intel X-540 AT2 card on the same
> > systems and the latency was on the order of 4-5 microseconds.
> 
> Thanks for reporting.
> This is the first time we hit such scenario, we will check it internally and will get back to you with answers. 

Back to this topic, could it be the same issue as reported by Sagi,
"mlx5 high latency observed on send operations" [1]?

The related patches have been submitted and are on track for DPDK 17.11.
While they are not yet on the master tree, you can find them on
dpdk-next-net.

[1] http://dpdk.org/ml/archives/dev/2017-August/073081.html

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2017-09-04 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 18:39 Arjun Roy
2017-06-29  5:26 ` Shahaf Shuler
2017-09-04 15:52   ` Adrien Mazarguil [this message]
2017-09-04 17:12     ` Nélio Laranjeiro

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=20170904155252.GZ4301@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=arroy@eng.ucsd.edu \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=shahafs@mellanox.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).