From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] [RFC] pselect01: Tune thresholds
Date: Mon, 15 May 2017 09:15:36 -0400 (EDT) [thread overview]
Message-ID: <623640767.11529328.1494854136525.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <59198103.4070308@cn.fujitsu.com>
----- Original Message -----
> Hi Jan and Cyril,
>
> Did you get the following error message when running pselect01 on
> RHEL5.11GA (physical machine):
> =====================================================================================
> [root@RHEL5U11ga_Intel64 pselect]# ./pselect01
> tst_test.c:847: INFO: Timeout per run is 0h 05m 00s
> pselect01.c:62: INFO: pselect() sleeping for 1 secs 0 nsec 1 iterations
> pselect01.c:95: PASS: pselect() slept for 1000443us, requested
> 1000000us, treshold 10200
> pselect01.c:62: INFO: pselect() sleeping for 0 secs 1000000 nsec 100
> iterations
> pselect01.c:95: PASS: pselect() slept for 101455us, requested 100000us,
> treshold 21000
> pselect01.c:62: INFO: pselect() sleeping for 0 secs 2000000 nsec 100
> iterations
> pselect01.c:95: PASS: pselect() slept for 203069us, requested 200000us,
> treshold 22000
> pselect01.c:62: INFO: pselect() sleeping for 0 secs 10000000 nsec 10
> iterations
> pselect01.c:83: FAIL: pselect() woken up too early 99536us, expected
> 100000us
> pselect01.c:62: INFO: pselect() sleeping for 0 secs 100000000 nsec 1
> iterations
> pselect01.c:95: PASS: pselect() slept for 100559us, requested 100000us,
> treshold 1200
> =====================================================================================
>
> It seems that pselect woke up early on RHEL5.11GA.
Yes, I see that too. It fails pretty often, even on KVM guest.
pselect6(0, [], NULL, NULL, {0, 2000000}, {NULL, 8}) = 0 (Timeout) <0.001822>
pselect6(0, [], NULL, NULL, {0, 10000000}, {NULL, 8}) = 0 (Timeout) <0.009775>
pselect6(0, [], NULL, NULL, {0, 100000000}, {NULL, 8}) = 0 (Timeout) <0.099808>
next prev parent reply other threads:[~2017-05-15 13:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 14:16 [LTP] [PATCH v2] [RFC] pselect01: Tune thresholds Cyril Hrubis
2017-05-15 10:03 ` Jan Stancek
2017-05-15 10:20 ` Xiao Yang
2017-05-15 13:15 ` Jan Stancek [this message]
2017-05-15 13:23 ` Cyril Hrubis
2017-05-15 12:36 ` Cyril Hrubis
2017-05-15 13:00 ` Jan Stancek
2017-05-15 13:13 ` Cyril Hrubis
2017-05-15 13:16 ` Jan Stancek
2017-05-22 8:39 ` Jan Stancek
2017-05-22 12:04 ` Cyril Hrubis
2017-05-22 13:37 ` Jan Stancek
2017-05-22 13:19 ` Cyril Hrubis
2017-05-22 14:57 ` Jan Stancek
2017-05-22 15:15 ` Cyril Hrubis
2017-05-23 7:54 ` Jan Stancek
2017-05-23 9:16 ` Cyril Hrubis
2017-05-23 9:45 ` Jan Stancek
2017-06-02 12:48 ` Jan Stancek
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=623640767.11529328.1494854136525.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox