From: Andrea Arcangeli <andrea@suse.de>
To: safemode <safemode@speakeasy.net>
Cc: Robert Love <rml@ufl.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-ac10-preempt lmbench output.
Date: Wed, 10 Oct 2001 03:18:03 +0200 [thread overview]
Message-ID: <20011010031803.F8384@athlon.random> (raw)
In-Reply-To: <20011010003636Z271005-760+23005@vger.kernel.org>
In-Reply-To: <20011010003636Z271005-760+23005@vger.kernel.org>; from safemode@speakeasy.net on Tue, Oct 09, 2001 at 08:36:56PM -0400
On Tue, Oct 09, 2001 at 08:36:56PM -0400, safemode wrote:
> mp3 player to skip, though. That probably wont be fixed intil 2.5, since
> you need to have preemption in the vm and the rest of the kernel.
xmms skips during I/O should have nothing to do with preemption.
As Alan noted for the ring of dma fragments to expire you need a
scheduler latency of the order of seconds, now (assuming the ll points
in read/write paths) when we've bad latencies under writes it's of the
order of 10msec and it can be turned down further by putting preemption
checks in the buffer lru lists write paths.
The reason xmms skips I believe is because the vm is doing write
throttling. I've at least one idea on how to fix it but it has nothing
to do with preemption in the VM or whatever else scheduler related
thing.
So I wouldn't expect to fix any playback skips where buffering is
possible by using the preemptive patch etc.. It's nearly impossible that
it makes any difference.
The preemptive patch can matter only if you're doing real time signal
processing where any kind of buffering isn't possible.
Andrea
next prev parent reply other threads:[~2001-10-10 1:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 0:36 2.4.10-ac10-preempt lmbench output safemode
2001-10-10 1:18 ` Andrea Arcangeli [this message]
2001-10-10 2:09 ` safemode
2001-10-10 2:10 ` Robert Love
2001-10-10 2:51 ` Andrea Arcangeli
[not found] ` <20011010020935.50DEF1E756@Cantor.suse.de>
2001-10-10 2:30 ` Andrea Arcangeli
2001-10-10 2:37 ` Robert Love
2001-10-10 3:06 ` Andrea Arcangeli
2001-10-10 3:24 ` Robert Love
2001-10-10 4:03 ` Andrea Arcangeli
2001-10-12 13:22 ` Pavel Machek
2001-10-13 20:42 ` Mike Fedyk
2001-10-13 23:21 ` Robert Love
2001-10-14 6:18 ` Pavel Machek
2001-10-10 5:25 ` Justin A
2001-10-10 19:42 ` Buffers, dbench and latency Roger Larsson
[not found] <200110100036.UAA128640@ufl.edu>
2001-10-10 2:02 ` 2.4.10-ac10-preempt lmbench output Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 3:57 Dieter Nützel
[not found] <200110100358.f9A3wSB17421@zero.tech9.net>
2001-10-10 4:02 ` Robert Love
2001-10-10 4:04 ` Robert Love
2001-10-10 4:27 ` Andrea Arcangeli
[not found] <20011010035818.A556B1E760@Cantor.suse.de>
2001-10-10 4:23 ` Andrea Arcangeli
2001-10-10 4:42 ` Dieter Nützel
[not found] ` <20011010044242.82D131E768@Cantor.suse.de>
2001-10-10 4:48 ` Andrea Arcangeli
[not found] <200110100358.NAA17519@isis.its.uow.edu.au>
2001-10-10 5:13 ` Andrew Morton
2001-10-10 5:26 ` Andrea Arcangeli
2001-10-10 11:41 ` safemode
2001-10-10 12:00 ` safemode
[not found] ` <20011010120009.851921E7C9@Cantor.suse.de>
2001-10-10 13:36 ` Andrea Arcangeli
2001-10-10 15:37 ` Dieter Nützel
2001-10-10 20:10 ` Justin A
2001-10-10 23:42 ` safemode
2001-10-11 0:30 ` Mike Fedyk
2001-10-10 18:14 ` 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=20011010031803.F8384@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@ufl.edu \
--cc=safemode@speakeasy.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