From: Nick Piggin <piggin@cyberone.com.au>
To: Sonika Sachdeva <sonikam@magnum.barc.ernet.in>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Linux scheduler Implementation details
Date: Fri, 27 Feb 2004 21:59:22 +1100 [thread overview]
Message-ID: <403F230A.9030200@cyberone.com.au> (raw)
In-Reply-To: <403F2306.C51C75E8@magnum.barc.ernet.in>
Sonika Sachdeva wrote:
>I wonder if you could give me some hints to do fair approximations (to calculate
>execution time) for scheduling process?
>
>
Use a very simple model? Assume each runnable process gets equal
amount of the CPU.
I have no idea what you are trying to do or why, but I suspect
that the "simulator" you should be using is testing a running
kernel on a real machine. Very simple, very accurate.
prev parent reply other threads:[~2004-02-27 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 9:18 Linux scheduler Implementation details Sonika Sachdeva
2004-02-27 9:21 ` Raj
2004-02-27 9:24 ` Nick Piggin
2004-02-27 9:46 ` Sonika Sachdeva
2004-02-27 10:07 ` Nick Piggin
2004-02-27 10:59 ` Sonika Sachdeva
2004-02-27 10:59 ` Nick Piggin [this message]
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=403F230A.9030200@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sonikam@magnum.barc.ernet.in \
/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