From: Philippe.LAFFONT@st.com
To: linux-kernel@vger.kernel.org
Subject: Strange behaviour of the Round Robin policy
Date: Thu, 14 Jun 2001 15:19:17 +0200 [thread overview]
Message-ID: <H00006240b52eb6d@MHS> (raw)
[-- Attachment #1: cc:Mail --]
[-- Type: text/plain, Size: 1198 bytes --]
I'm using RedHat Linux V2.2.13 and I made the following test:
I launched 10 times the same program with priority 10 of Round Robin
policy (from a shell having priority 20 of FIFO policy). Each program
does an infinite busy loop (while (1)).
One minute later, I launched the "ps" command and I was expected that
the TIME values of all these processes are in an interval which is T
large, where T is given by sched_rr_get_interval() i.e. T=150ms in
this release.
But the ps result was:
PID TTY TIME CMD
652 tty1 00:00:00 login
1549 tty1 00:00:00 bash
1566 tty1 00:00:00 bash
1596 tty1 00:01:12 my_program
1597 tty1 00:00:02 my_program
1598 tty1 00:00:01 my_program
1599 tty1 00:00:01 my_program
1600 tty1 00:00:05 my_program
1601 tty1 00:00:01 my_program
1602 tty1 00:00:00 my_program
1603 tty1 00:00:16 my_program
1604 tty1 00:00:01 my_program
1605 tty1 00:00:00 my_program
1610 tty1 00:00:00 ps
Does someone have any explanation of this behavior? Thanks in advance.
reply other threads:[~2001-06-14 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=H00006240b52eb6d@MHS \
--to=philippe.laffont@st.com \
--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