public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sean Estabrooks" <seanlkml@rogers.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sched-2.5.64-D3, more interactivity changes
Date: Mon, 17 Mar 2003 19:28:43 -0500	[thread overview]
Message-ID: <001301c2ece5$557ee280$c70a0a0a@slappy> (raw)

On Mon, 17 Mar 2003 11:21:33 +0100, Ingo Molnar wrote:

> the attached patch (against BK-curr) implements more finegrained timeslice
> distribution, without changing the total balance of timeslices, by
> recalculating the priority of CPU-bound tasks at a finer granularity, and
> by roundrobining tasks. Right now this new granularity is 50 msecs (the
> default timeslice for default priority tasks is 100 msecs).
>
> Could people, who can reproduce 'audio skips' kind of problems even with
> BK-curr, give this patch a go?
>
>       Ingo

An enthusiastic, Works For Me (tm)....

Linux version 2.5.64
(gcc version 3.2.2 20030217 (Red Hat Linux 8.0 3.2.2-2))

model name  : Pentium III (Coppermine)
stepping        : 1
cpu MHz      : 647.134
cache size     : 256 KB
bogomips      : 1277.95

Cheers,
Sean


             reply	other threads:[~2003-03-18  0:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18  0:28 Sean Estabrooks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-19 11:40 [patch] sched-2.5.64-D3, more interactivity changes Felipe Alfaro Solana
2003-03-19 11:30 Felipe Alfaro Solana
2003-03-17 10:21 Ingo Molnar
2003-03-17 18:01 ` Martin J. Bligh
2003-03-19  5:52 ` Andrew Morton
2003-03-19  6:31   ` Joshua Kwan
2003-03-19  7:13   ` Jeremy Fitzhardinge
2003-03-19  8:21     ` Mike Galbraith
2003-03-19 16:37       ` Jeremy Fitzhardinge
2003-03-19 16:51       ` Jim Houston

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='001301c2ece5$557ee280$c70a0a0a@slappy' \
    --to=seanlkml@rogers.com \
    --cc=linux-kernel@vger.kernel.org \
    /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