From: shreenivasa H V <shreenihv@usa.net>
To: Mike Kravetz <kravetz@us.ibm.com>, shreenivasa H V <shreenihv@usa.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Re: scheduler policy]
Date: 13 Sep 2001 23:41:11 CDT [thread overview]
Message-ID: <20010914044111.3882.qmail@nwcst281.netaddress.usa.net> (raw)
thanks, and I have a related question. Consider we have only 2 processes with
equal priority. Now one of them is switched out for an i/o operation. The
second one gains the cpu and executes past its time quantum. Since the other
process is not yet ready this process continues to enjoy the cpu. Now will
this usage be accounted for a new time quantum for this second process or will
it be unaccounted. According to what I understand, the second process will not
start its new time quantum until the epoch has ended i.e., the first one also
has finished its time quantum. So does this mean the epoch will never end
until there is a process in the system who's time quantum is yet to be
expired?
shreeni.
next reply other threads:[~2001-09-14 4:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 4:41 shreenivasa H V [this message]
2001-09-14 7:44 ` [Re: scheduler policy] george anzinger
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=20010914044111.3882.qmail@nwcst281.netaddress.usa.net \
--to=shreenihv@usa.net \
--cc=kravetz@us.ibm.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;
as well as URLs for NNTP newsgroup(s).