DPDK usage discussions
 help / color / mirror / Atom feed
From: dave seddon <dave.seddon.ca@gmail.com>
To: maruko.kwok@gmail.com
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] what is the average latency you get for io forwarding from dpdk?
Date: Tue, 17 Jan 2017 06:41:22 -0800	[thread overview]
Message-ID: <CANypexQtNwP=Z3Mjwp=A3byXHDi0=N+6SW38d2SbWcsb4NbT2Q@mail.gmail.com> (raw)
In-Reply-To: <CAE56PLtqN7o5bSuJKjYXg_rDs7m0WjOm=kX9EQ_zCWbE1tKzdA@mail.gmail.com>

There's an interesting video about speed:
https://youtu.be/ne3svryuthI

On Jan 17, 2017 12:28 AM, "Marco Kwok" <maruko.kwok@gmail.com> wrote:

> Hello all,
>
> I wonder if anyone could get a relative low latency from dpdk on 1gb link.
>
> When using testpmd, an packet of 150 bytes is sent, packet is received by
> the port and loopback to the sender.
> I usually could get 50us for io forward. Sometime it can be as fast as 3us.
> However it is too slow to be used for switching application.
>
> My test platform is on a intel NUC NUC5I5RYH, which has i5 5250U 1.6GHz,
> 16GB DDR3 and i218-V network chip. dpdk 16.07.2
>
>
> I have done the following things try to get a better latency with no luck:
> -setup 1G hugepages
> -disable cpu frequency scaling to make sure cpu runs at max speed of 2.7GHz
> -isolate a cpu core from kernel task scheduler by isolcpus
> -setting the burst size of testpmd to 1
>
> Guys, I really want your input. I don't need high throughput but low
> latency. Does anyone of you have been able to achieve a lower latency with
> dpdk? I don't see the advantage I have taken from dpdk now.
>
> Best,
> Mark
>

  reply	other threads:[~2017-01-17 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17  8:28 Marco Kwok
2017-01-17 14:41 ` dave seddon [this message]
2017-01-18 16:03 ` Pavel Shirshov
2017-01-18 16:55 ` Stephen Hemminger

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='CANypexQtNwP=Z3Mjwp=A3byXHDi0=N+6SW38d2SbWcsb4NbT2Q@mail.gmail.com' \
    --to=dave.seddon.ca@gmail.com \
    --cc=maruko.kwok@gmail.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).