public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Matt Mackall <mpm@selenic.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	ck list <ck@vds.kolivas.org>
Subject: Re: [PATCH] [RSDL 5/6] sched: implement rsdl cpu scheduler
Date: Tue, 6 Mar 2007 08:11:21 +1100	[thread overview]
Message-ID: <200703060811.21316.kernel@kolivas.org> (raw)
In-Reply-To: <20070305203857.GQ16722@waste.org>

On Tuesday 06 March 2007 07:38, Matt Mackall wrote:
> On Sun, Mar 04, 2007 at 06:06:22PM +1100, Con Kolivas wrote:
> > + * This is the time all tasks within the same priority round robin.
> > + * Set to a minimum of 6ms.
> >   */
> > +#define RR_INTERVAL		((6 * HZ / 1001) + 1)
>
> What happens with small HZ? Like 100? I suppose 10ms is a reasonable
> number here. But in general, how well does this scheduler do without a
> time source other than jiffies?

Perfectly fine at 100. It only needs to do accounting during a busy tick, and 
on dynticks we always service a timer interrupt during that busy tick so it 
works fine there as well. In fact, choosing a lower HZ you are indirectly 
making a decision that you don't value latency as much as at the higher HZ 
and 10ms is fine for the scheduling there. It would be possible to service 
the cpu accounting with any timer that fired at at least 100HZ even if there 
was some way to turn ticks off fully when the cpu is busy (which there isn't 
currently a way to do).

-- 
-ck

      parent reply	other threads:[~2007-03-05 21:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04  7:06 [PATCH] [RSDL 5/6] sched: implement rsdl cpu scheduler Con Kolivas
2007-03-05 20:38 ` Matt Mackall
2007-03-05 21:05   ` Gene Heskett
2007-03-05 21:11   ` Con Kolivas [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=200703060811.21316.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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