From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Why do processes with higher priority to be allocated more timeslice?
Date: Tue, 27 Sep 2011 11:28:46 +0700 [thread overview]
Message-ID: <CAGdaada=uKEWYUXGCzufTwnsR5K_-DK=GEYL4C5xFN0Ggxr8bw@mail.gmail.com> (raw)
In-Reply-To: <CAOXENUhLumEtR5D8QCcMDVVc254CocjCUszOYWqkwe1VfDZKJQ@mail.gmail.com>
Hi :)
On Tue, Sep 27, 2011 at 09:07, Parmenides <mobile.parmenides@gmail.com> wrote:
> Actually, a common characteristics of Linux's schedulers is that
> timeslices will be longer with priorities raising .
generally I agree with that.... :)
> I am just curious
> about why the the schedulers takes this policy.
simply to say that, the more important a job is, it should be given
longer time to run... but, the process has privilege to yield before
time slice is up...and when it comes back,it will use the remaining
time slice.....and its dynamic priority will stay the same (that's the
property that I recall....)
>IMHO, this policy
> somewhat conflicts with intuition. I think there must be some
> motivations to take this policy, but I have no idea about it.
well, you can think, what happen if you take the other direction for
the policy? higher priority, but less time slice? that, IMHO, is less
intuitive.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-09-27 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 2:16 Why do processes with higher priority to be allocated more timeslice? Parmenides
2011-09-26 7:51 ` Mulyadi Santosa
2011-09-26 17:10 ` Parmenides
2011-09-26 18:40 ` Jeff Donner
2011-09-27 2:07 ` Parmenides
2011-09-27 4:28 ` Mulyadi Santosa [this message]
2011-09-27 13:06 ` Parmenides
2011-09-27 15:44 ` Mulyadi Santosa
2011-10-07 15:40 ` Sri Ram Vemulpali
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='CAGdaada=uKEWYUXGCzufTwnsR5K_-DK=GEYL4C5xFN0Ggxr8bw@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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.