From: Stephen Hemminger <stephen@networkplumber.org>
To: Vincenzo Maffione <v.maffione@gmail.com>
Cc: maverickjin88@gmail.com, users@dpdk.org
Subject: Re: [dpdk-users] Why DPDK latency is high when sending message in interval?
Date: Mon, 29 Oct 2018 08:23:39 -0700 [thread overview]
Message-ID: <20181029082339.15d4ebee@xeon-e3> (raw)
In-Reply-To: <CA+_eA9hxMOzQqXjnJ5F+y=+8fFrA_vjNt7L8VvHNVO5RzcqJtw@mail.gmail.com>
On Sun, 28 Oct 2018 09:07:02 +0100
Vincenzo Maffione <v.maffione@gmail.com> wrote:
> If you don't care about CPU utilization, busy-wait is the way to go.
> Otherwise you can try to usleep() for something like 60-70 us (to lower the
> CPU utilization), and then busy-wait for the rest of the interval (so that
> you still have maximum precision).
>
> You may want to have a look at this
> https://academic.oup.com/comjnl/article/61/6/808/4259797 , specially
> sections 4.3 and 4.1.
>
> Cheers,
> Vincenzo
>
> Il giorno dom 28 ott 2018 alle ore 09:01 Sungho Hong <
> maverickjin88@gmail.com> ha scritto:
>
> > Thank you very much for the reply.
> > But in that case, should I busy wait, to create the delay?
> >
> >
> >
>
If doing very brief and exact sleep, you should change your thread priority to
one of the Real Time classes.
next prev parent reply other threads:[~2018-10-29 15:23 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
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 [this message]
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=20181029082339.15d4ebee@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=maverickjin88@gmail.com \
--cc=users@dpdk.org \
--cc=v.maffione@gmail.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).