public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] poll02 threshold overruns
Date: Tue, 22 Mar 2016 10:27:36 +0100	[thread overview]
Message-ID: <20160322092735.GA9410@rei.lan> (raw)
In-Reply-To: <SN1PR12MB07827ABE2B50365F2C528A03EE8F0@SN1PR12MB0782.namprd12.prod.outlook.com>

Hi!
> I'm working on PowerPc based board MPC8360 and we are running 4.1.13 kernel. During our LTP run, we saw the following failure with poll02 test.
> 
> poll02      1  TFAIL  :  poll02.c:92: poll() slept too long 115ms, expected 100ms, threshold 12
> 
> The log file is attached to this mail.
> 
> Please note that I'm running the latest LTP code.
> 
> I understand that threshold value overruns the relax limit. I try changing the threshold value to 20 as below (to give more relaxing time)
> 
> testcases/kernel/syscalls/poll/poll02.c, line 61
> 
> - treshold = sleep_ms / 100 + 10;
> +treshold = sleep_ms / 10 + 10;
> 
> I ran the test in a loop until it fails and the test failed after 3 mins at attempt number 240 with the timer value 121ms. Error as below:
> 
> poll02      1  TFAIL  :  poll02.c:92: poll() slept too long 121ms, expected 100ms, threshold 20
> 
> 
> Can you please look into this and explain the behaviour and a possible solution? Is it a architecture constraint?

The thresholds were set up by trial and error on older PC. The timer
overruns have no real upper cap and they depends on CPU speed, kernel
.config parameters and system load.

So it possibly may fail on slow embedded machines. I guess that what we
should do is to move the treshold computation into the test library so
that we can tweak the value in one place and either do some heuristic or
provide a way to override it by user.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2016-03-22  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 21:23 [LTP] poll02 threshold overruns Kshitij Malik
2016-03-22  9:27 ` Cyril Hrubis [this message]
2016-03-22 14:28   ` Kshitij Malik
2016-03-22 14:44     ` Cyril Hrubis
2016-03-22 15:26       ` Kshitij Malik

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=20160322092735.GA9410@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox