mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tsafrir Dan <dants@cs.huji.ac.il>
To: linux-kernel@vger.kernel.org
Cc: etsman@cs.huji.ac.il, feit@cs.huji.ac.il
Subject: the value of PROC_CHANGE_PENALTY
Date: Sun, 03 Jun 2001 19:06:38 +0300	[thread overview]
Message-ID: <3B1A608E.21AE7C5B@cs.huji.ac.il> (raw)

as I understand, for i386 in Linux-2.2.x the default length
of a quantum was 200ms, and in 2.4.x it had changed to 50ms
(
 according to the following 2.4.5 sched.c code:

    #if HZ < 200
    #define TICK_SCALE(x)   ((x) >> 2)
    ...
    #define NICE_TO_TICKS(nice)     (TICK_SCALE(20-(nice))+1)
    ...
    /* in the `recalculate' portion of schedule(): ... */
    for_each_task(p)
        p->counter = (p->counter >> 1) + NICE_TO_TICKS(p->nice);
)

But, 
the value of PROC_CHANGE_PENALTY was not changed accordingly, and is 
still 15. This means that the result of the following goodness() code:
    if (p->processor == this_cpu)
        weight += PROC_CHANGE_PENALTY;
is that any task that executed on `this_cpu' (goodness > 15) 
will always be more "desirable" then a task that executed on 
another cpu (goodness <= 6) which was not the case in 2.2.x .

am I correct ?
and if so, is this what the authors meant, or did they simply forget
to update PROC_CHANGE_PENALTY's value when moving from 2.2 to 2.4 ?

please cc me: dants@cs.huji.ac.il
thanks, dan.

             reply	other threads:[~2001-06-03 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03 16:06 Tsafrir Dan [this message]
     [not found] <Pine.LNX.4.10.10106042004010.8516-100000@coffee.psychology.mcmaster.ca>
2001-06-05 19:05 ` Tsafrir Dan

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=3B1A608E.21AE7C5B@cs.huji.ac.il \
    --to=dants@cs.huji.ac.il \
    --cc=etsman@cs.huji.ac.il \
    --cc=feit@cs.huji.ac.il \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®