From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Robert Love" <rml@tech9.net>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.10-ac10-preempt lmbench output.
Date: Wed, 10 Oct 2001 07:26:07 +0200 [thread overview]
Message-ID: <20011010072607.P726@athlon.random> (raw)
In-Reply-To: <200110100358.NAA17519@isis.its.uow.edu.au> <3BC3D916.B0284E00@zip.com.au>
In-Reply-To: <3BC3D916.B0284E00@zip.com.au>; from akpm@zip.com.au on Tue, Oct 09, 2001 at 10:13:58PM -0700
On Tue, Oct 09, 2001 at 10:13:58PM -0700, Andrew Morton wrote:
> I don't understand why Andrea is pointing at write throttling? xmms
> doesn't do any disk writes, does it??
Of course it doesn't. You're right it could be just because of I/O
bandwith shortage. But it could really be also because of vm write
throttling.
xmms can end waiting I/O completion for I/O submitted by other I/O bound
tasks. This because xmms is reading from disk and in turn it is
allocating cache and in turn it is allocating memory. While allocating
memory it may need to write throttle.
Copying the file to /dev/shm fixed the problem but that would cover both
the write throttling and the disk bandwith problems at the same time and
I guess it's a mixed effect of both things.
> Andrea's VM has a rescheduling point in shrink_cache(), which is the
> analogue of the other VM's page_launder(). This rescheduling point
> is *absolutely critial*, because it opens up what is probably the
> longest-held spinlock in the kernel (under common use). If there
> were a similar reschedulig point in page_launder(), comparisons
> would be more valid...
Indeed.
> I would imagine that for a (very) soft requirement such as audio
> playback, the below patch, combined with mlockall and renicing
> should fix the problems. I would expect that this patch will
> give effects which are similar to the preempt patch. This is because
I didn't checked the patch in the detail yet but it seems you covered
read/write some bits in /proc and a lru list during buffer flushing. I
agree that it should be enough to give the same effects of the preempt
patch.
> most of the other latency problems are under locks - icache/dcache
> shrinking and zap_page_range(), etc.
Exactly.
> This patch should go into the stock 2.4 kernel.
>
> Oh. And always remember to `renice -19' your X server.
I don't renice my X server (I rather renice all cpu hogs to +19 and I
left -20 for something that really needs to run as fast as possible
regardless of the X server).
Andrea
next prev parent reply other threads:[~2001-10-10 5:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200110100358.NAA17519@isis.its.uow.edu.au>
2001-10-10 5:13 ` 2.4.10-ac10-preempt lmbench output Andrew Morton
2001-10-10 5:26 ` Andrea Arcangeli [this message]
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
[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.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
2001-10-10 3:57 Dieter Nützel
[not found] <200110100036.UAA128640@ufl.edu>
2001-10-10 2:02 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 0:36 safemode
2001-10-10 1:18 ` Andrea Arcangeli
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
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=20011010072607.P726@athlon.random \
--to=andrea@suse.de \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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