All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] [PATCH] pselect01: Tune thresholds
Date: Fri, 12 May 2017 15:17:30 +0200	[thread overview]
Message-ID: <20170512131730.GA25149@rei.lan> (raw)
In-Reply-To: <trinity-29096542-6ccc-407c-b312-5b55c487a1f3-1494583440399@3capp-gmx-bs13>

Hi!
> Additionally, please keep in mind that on some architectures the
> time measured is based on the jiffies clock resolution which depends
> on the CONFIG_HZ value and results in a resolutions of e.g. 0.01, 
> 0.004, or 0.001 seconds which is way above the resolution you get
> on the x86 platform (with the TSC clock).
> 
> This testcase was failing for me on the parisc platform because of this inaccuracy.
> 
> Maybe the resolution of the CLOCK_MONOTONIC clock (which is basically used in this
> test) should be checked with clock_getres() and it's result included in the calculation?

Right, I've dusted off old pxa270 and indeed we cannot measure less than
20us interval there. But clock_getres() returns 10ms which is much more
than the actuall measured value...

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2017-05-12 13:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 13:18 [LTP] [RFC] [PATCH] pselect01: Tune thresholds Cyril Hrubis
2017-05-11 12:29 ` Cyril Hrubis
2017-05-11 15:54 ` Jan Stancek
2017-05-12  6:51   ` Cyril Hrubis
2017-05-12  7:11     ` Jan Stancek
2017-05-12  7:17       ` Cyril Hrubis
2017-05-12  7:33         ` Jan Stancek
2017-05-12 10:04           ` Helge Deller
2017-05-12 13:17             ` Cyril Hrubis [this message]
2017-05-12 13:59               ` Cyril Hrubis
2017-05-12 15:38           ` Cyril Hrubis

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=20170512131730.GA25149@rei.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.