DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] "No probed ethernet devices" caused by inaccurate msec_delay()
Date: Tue, 28 Jan 2014 10:13:09 -0800	[thread overview]
Message-ID: <20140128101309.639a1b88@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <201401281723.22155.thomas.monjalon@6wind.com>

TSC has lots of platform related issues. It is not guaranteed sync'd across physical
packages and AMD boxes have lots of problems.

Why does delay_ms not just use nanosleep() and let the OS worry about it?
On a related note, I have found that putting the worker (non master) threads
into real time scheduling class also helps.

      reply	other threads:[~2014-01-28 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27  2:56 Sangjin Han
2014-01-27  9:19 ` Thomas Monjalon
2014-01-28  1:16   ` Sangjin Han
2014-01-28 16:23     ` Thomas Monjalon
2014-01-28 18:13       ` Stephen Hemminger [this message]

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=20140128101309.639a1b88@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).