public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: as / scheduler question
Date: Tue, 29 Jul 2003 09:08:09 +1000	[thread overview]
Message-ID: <200307290908.09065.kernel@kolivas.org> (raw)

Nick

With the sheduler work Ingo and I have been doing I was wondering if there was 
possibly a problem with requeuing kernel threads at certain intervals? Ingo's 
current version requeues all threads at 25ms and I just wondered if this 
number might be a multiple or factor of a magic number in the AS workings, as 
we're seeing a few changes in behaviour with AS only. I'm planning on leaving 
kernel threads out of this requeuing, but I thought I could also pick your 
brain.

Con


             reply	other threads:[~2003-07-28 23:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 23:08 Con Kolivas [this message]
2003-07-28 23:01 ` as / scheduler question Andrew Morton
2003-07-28 23:25   ` Con Kolivas
2003-07-28 23:32     ` Robert Love
2003-07-31  6:43     ` Nick Piggin
2003-07-31  6:45     ` Nick Piggin
2003-07-28 23:30   ` Robert Love

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=200307290908.09065.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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