From: Matti Aarnio <matti.aarnio@zmailer.org>
To: "James C. Owens" <owensjc@bellatlantic.net>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: O(1) scheduler ver H6 - more straightforward timeslice macros
Date: Sat, 12 Jan 2002 23:59:45 +0200 [thread overview]
Message-ID: <20020112235945.G1914@mea-ext.zmailer.org> (raw)
In-Reply-To: <3C408B78.6050102@bellatlantic.net>
In-Reply-To: <3C408B78.6050102@bellatlantic.net>; from owensjc@bellatlantic.net on Sat, Jan 12, 2002 at 02:16:08PM -0500
On Sat, Jan 12, 2002 at 02:16:08PM -0500, James C. Owens wrote:
> Ingo,
>
> I like the new scheduler. It seems like the timeslice macros in sched.h
> could be more straighforward - i.e. instead of
(I quote too much, but to illustriate the point...)
> #define PRIO_TO_TIMESLICE(p) \
> ((( (MAX_USER_PRIO-1-USER_PRIO(p))*(MAX_TIMESLICE-MIN_TIMESLICE) + \
> MAX_USER_PRIO-1) / MAX_USER_PRIO) + MIN_TIMESLICE)
>
> #define RT_PRIO_TO_TIMESLICE(p) \
> ((( (MAX_RT_PRIO-(p)-1)*(MAX_TIMESLICE-MIN_TIMESLICE) + \
> MAX_RT_PRIO-1) / MAX_RT_PRIO) + MIN_TIMESLICE)
>
> why not
>
> #define PRIO_TO_TIMESLICE(p) \
> (MAX_TIMESLICE -
> (USER_PRIO(p)/(MAX_USER_PRIO-1))*(MAX_TIMESLICE-MIN_TIMESLICE))
>
> #define RT_PRIO_TO_TIMESLICE(p) \
> (MAX_TIMESLICE - (p/(MAX_RT_PRIO-1))*(MAX_TIMESLICE-MIN_TIMESLICE))
>
>
> The second way seems simpler to me, and really illustrates what you are
> doing in a more straightforward manner.
Except that the math is INTEGER, not floating-point,
which means that this way you loose precission.
You HAVE TO do multiplications first, only then (finally) the division.
Depending the value-spaces, small-enough value-spaces might be
turnable into table mappings. However that has lots of dependencies
in hardware architecture, e.g. memory access speeds, cache pollution,
speed of multiply/divide operations, etc.
If dividers/multipliers are constants, and powers of two, the math
can happen with constant shifts, which are fast at all systems.
If not, things get rather complicated. (And thus a careless -1,
or lack of one, may be costly.)
> I also cleaned up some of the comments. The sched.h diff between the H6
> version of the scheduler applied to 2.4.18-pre3 and vanilla 2.4.18-pre3
> follows: (Note that I changed the min and max timeslices to 20 and 100
> for my own use.)
...
"uni-diff please, use '-u' option for the diff"
> To lkml - please cc me on any response, as I do not subscribe to the
> lkml - I read it via a news gateway.
>
>
> Jim Owens
/Matti Aarnio
next prev parent reply other threads:[~2002-01-12 22:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 19:16 James C. Owens
2002-01-12 21:59 ` Matti Aarnio [this message]
2002-01-12 22:18 ` James C. Owens
2002-01-13 18:08 ` Ingo Molnar
2002-01-13 18:42 ` James C. Owens
2002-01-13 20:55 ` Ingo Molnar
2002-01-14 18:59 ` 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=20020112235945.G1914@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=owensjc@bellatlantic.net \
/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
all inboxes | Powered by JetHome®