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 20:24:39 +1100 [thread overview]
Message-ID: <403F0CD7.5080305@cyberone.com.au> (raw)
In-Reply-To: <403F0B66.A7920233@magnum.barc.ernet.in>
Sonika Sachdeva wrote:
>Hello List,
>
>I want to simulate the Linux Scheduler, ie Calculate the priorities, counters
>and define to some extent how much time a given process will take to execute on
>the system. Can anyone suggest some pointers?
>
>
It is all in kernel/sched.c, so you can just make a simulator and
plug that code in.
This will perfectly model the scheduler behaviour given some input
from your simulator, which is what you asked for. This has nothing
to do with maximum realtime scheduling latency, of course.
next prev parent reply other threads:[~2004-02-27 9:24 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 [this message]
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
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=403F0CD7.5080305@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