LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: akpm@linux-foundation.org, Bill Irwin <bill.irwin@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arjan@linux.intel.com
Subject: Re: [PATCH (update 3)] timer: Run calc_load halfway through each round_jiffies second
Date: Fri, 2 Mar 2007 17:35:55 +0100 [thread overview]
Message-ID: <200703021735.55142.dada1@cosmosbay.com> (raw)
In-Reply-To: <45E83F7A.9030307@simon.arlott.org.uk>
On Friday 02 March 2007 16:15, Simon Arlott wrote:
> Whenever jiffies is started at a multiple of 5*HZ or wraps, calc_load is
> run exactly on the second which is when tasks using round_jiffies will
> be scheduled to run. This has a bad effect on the load average, making
> it tend towards 1.00 if a task happens to run every time the load is
> being calculated.
>
> This changes calc_load so that it updates load half a second after any
> tasks scheduled using round_jiffies.
>
Simon
I believe this patch is too complex/hazardous and may break exp decay
computation.
(Even if nobody care about avenrun[] those days :), do you ? )
You could just change LOAD_FREQ from (5*HZ) to (5*HZ+1)
#define LOAD_FREQ (5*HZ+1)
Mathematical proof (well... sort of)
$ cat prog.c
#define FSHIFT 11 /* nr of bits of precision */
#define FIXED_1 ((double)(1<<FSHIFT)) /* 1.0 as fixed-point */
#include <math.h>
#include <stdio.h>
int main()
{
printf("Old values :\n");
printf("#define EXP_1 %g\n", FIXED_1/exp(5.0/60.0));
printf("#define EXP_5 %g\n", FIXED_1/exp(5.0/(5*60.0)));
printf("#define EXP_15 %g\n", FIXED_1/exp(5.0/(15*60.0)));
printf("New values :\n");
printf("%g\n", FIXED_1/exp(5.01/60.0));
printf("%g\n", FIXED_1/exp(5.01/(5*60.0)));
printf("%g\n", FIXED_1/exp(5.01/(15*60.0)));
return 0;
}
# gcc -o prog prog.c -lm
# ./prog
Old values :
#define EXP_1 1884.25
#define EXP_5 2014.15
#define EXP_15 2036.65
New values :
1883.94
2014.08
2036.63
You can see that 5.01 instead of 5.00 second gives the same EXP_xx values.
So (5*HZ + 1) is safe. (because HZ >= 100)
Eric
next prev parent reply other threads:[~2007-03-02 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 15:19 round_jiffies and load average Simon Arlott
2007-03-01 9:11 ` Simon Arlott
2007-03-01 18:52 ` [PATCH] timer: Add an initial 0.5s delay to calc_load Simon Arlott
2007-03-01 22:52 ` [PATCH (updated)] timer: Run calc_load halfway through each round_jiffies second Simon Arlott
2002-01-01 3:05 ` Pavel Machek
2007-03-05 22:35 ` Simon Arlott
2007-03-06 18:42 ` [PATCH (update 4)] " Simon Arlott
2007-03-06 22:20 ` [PATCH (updated)] " Chuck Ebbert
2007-03-01 23:10 ` Bill Irwin
2007-03-02 10:15 ` [PATCH (update 2)] " Simon Arlott
2007-03-02 15:15 ` [PATCH (update 3)] " Simon Arlott
2007-03-02 16:35 ` Eric Dumazet [this message]
2007-03-02 17:32 ` Simon Arlott
2007-03-02 18:03 ` Eric Dumazet
2007-03-02 20:14 ` Simon Arlott
2007-03-02 22:32 ` Eric Dumazet
2007-03-02 23:54 ` Simon Arlott
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=200703021735.55142.dada1@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bill.irwin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@fire.lp0.eu \
--subject='Re: [PATCH (update 3)] timer: Run calc_load halfway through each round_jiffies second' \
/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
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).