From: Vincenzo Maffione <v.maffione@gmail.com>
To: maverickjin88@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Why DPDK latency is high when sending message in interval?
Date: Sun, 28 Oct 2018 08:53:03 +0100 [thread overview]
Message-ID: <CA+_eA9i9rABQbzdvYyg3fQNE97qUFfRUj_gbEu+VDVt0cYvevw@mail.gmail.com> (raw)
In-Reply-To: <CAK8vx=hQ7YbbVhtXa-FveT7QXmmbJMYEkzzsSENDK0HSa9HiDQ@mail.gmail.com>
Hi,
How are you wating for the 100us interval? If you use sleep primitives
like usleep() or nanosleep() your delay is
likely due to the nanosleep() default timerslack, or deep C-states enabled,
or frequency scaling, etc.
This would be completely unrelated to DPDK.
Cheers,
Vincenzo
Il giorno dom 28 ott 2018 alle ore 01:36 Sungho Hong <
maverickjin88@gmail.com> ha scritto:
> Hello DPDK experts,
>
> I'am testing the performance of DPDK not on high speed polling
> but sending each packet with 100 microsecond interval.
>
> As same as the POSIX, DPDK performance degrades into 90 ~ 100 microsecond
> round-trip latency per 4KB message.
>
> Is there a way to improve the performance, when I am expecting to send the
> packet on 100 microsecond interval?
>
> And is there an explanation of the slowdown of DPDK when I am sending the
> packet on 100 microsecond interval?
>
> Any insights on this issue will be highly appreciated..
> Thanks
>
--
Vincenzo
next prev parent reply other threads:[~2018-10-28 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 23:36 Sungho Hong
2018-10-28 7:53 ` Vincenzo Maffione [this message]
2018-10-28 8:01 ` Sungho Hong
2018-10-28 8:07 ` Vincenzo Maffione
2018-10-28 10:15 ` Sungho Hong
2018-10-29 15:23 ` Stephen Hemminger
2018-10-29 15:25 ` Vincenzo Maffione
-- strict thread matches above, loose matches on Subject: below --
2018-10-26 20:37 Sungho Hong
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=CA+_eA9i9rABQbzdvYyg3fQNE97qUFfRUj_gbEu+VDVt0cYvevw@mail.gmail.com \
--to=v.maffione@gmail.com \
--cc=maverickjin88@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).