From: Valdis.Kletnieks@vt.edu
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] O10int for interactivity
Date: Mon, 28 Jul 2003 14:08:12 -0400 [thread overview]
Message-ID: <200307281808.h6SI8C5k004439@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 28 Jul 2003 01:12:16 +1000." <200307280112.16043.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
On Mon, 28 Jul 2003 01:12:16 +1000, Con Kolivas said:
> Here is a fairly rapid evolution of the O*int patches for interactivity thanks
> to Ingo's involvement.
I'm running the -O10 variant that's in Andrew's -test2-mm1 patch, and I'm
totally unable to force the CPU scheduler to misbehave.
I am, however, able to get 'xmms' to skip. The reason is that the CPU is being
scheduled quite adequately, but I/O is *NOT*.
The reason is that xmms's .ogg decoder is reading a 128K chunk every 10 seconds
or so, and doesn't do the next read till it's *really* close to running out of
data. Unfortunately, under high I/O load (which isn't all THAT high, it's a
HITACHI_DK23DA-40 in a Dell Laptop) it's possible for that 128K read to get
stuck behind other stuff that's doing heavy I/O (for instance, starting Mozilla
or OpenOffice, or sometime a 'find' command).
I'm guessing that the anticipatory scheduler is the culprit here. Soon as I figure
out the incantations to use the deadline scheduler, I'll report back....
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-07-28 17:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-27 15:12 [PATCH] O10int for interactivity Con Kolivas
2003-07-27 16:26 ` Wade
2003-07-27 19:15 ` Felipe Alfaro Solana
2003-07-28 7:51 ` Wiktor Wodecki
2003-07-28 7:55 ` Andrew Morton
2003-07-28 8:00 ` Wiktor Wodecki
2003-07-28 17:12 ` Jose Luis Domingo Lopez
2003-07-28 18:08 ` Valdis.Kletnieks [this message]
2003-07-28 18:40 ` Andrew Morton
2003-07-28 21:29 ` Wiktor Wodecki
2003-07-28 21:35 ` Andrew Morton
2003-07-31 6:36 ` Nick Piggin
2003-07-31 7:43 ` Con Kolivas
2003-07-31 7:58 ` Nick Piggin
2003-07-31 14:59 ` Jamie Lokier
2003-07-31 15:24 ` Oliver Neukum
2003-07-31 15:40 ` Jamie Lokier
2003-07-31 22:56 ` Nick Piggin
2003-08-04 18:51 ` [PATCH] O13int " Felipe Alfaro Solana
2003-08-04 18:58 ` Felipe Alfaro Solana
2003-08-04 21:46 ` Con Kolivas
2003-08-04 22:16 ` Felipe Alfaro Solana
2003-07-29 14:21 ` [PATCH] O10int " Timothy Miller
2003-07-29 14:35 ` Con Kolivas
2003-07-29 15:35 ` Timothy Miller
2003-07-30 1:16 ` Diego Calleja García
2003-07-30 1:36 ` Con Kolivas
2003-07-30 19:28 ` aradorlinux
2003-07-30 19:34 ` Andrew Morton
2003-07-29 15:28 ` Valdis.Kletnieks
2003-07-29 15:44 ` Timothy Miller
2003-07-29 15:45 ` Valdis.Kletnieks
2003-07-27 19:50 Voluspa
2003-07-28 2:05 Voluspa
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=200307281808.h6SI8C5k004439@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--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;
as well as URLs for NNTP newsgroup(s).