From: Nuno Monteiro <nuno@itsari.org>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Exaggerated swap usage
Date: Mon, 2 Dec 2002 01:01:44 +0000 [thread overview]
Message-ID: <20021202010144.GA728@hobbes.itsari.int> (raw)
In-Reply-To: <20021202002108.GQ28164@dualathlon.random>; from andrea@suse.de on Mon, Dec 02, 2002 at 00:21:08 +0000
On 02.12.02 00:21 Andrea Arcangeli wrote:
>
> ok, now it's clear what the problem is. there are inuse-dirty inodes
> that triggers a deadlock in the schedule-capable
> try_to_sync_unused_inodes of 2.4.20rc2aa1 (that avoided me to backout an
> otherwise corrupt lowlatency fix). It can trigger only in UP,
> in SMP the other cpu can always run kupdate that will flush all dirty
> inodes, so it would lockup one cpu as worse for 2.5 sec, this is
> probably why I couldn't reproduce it, I assume all of you reproducing
> the deadlock were running on an UP machine (doesn't matter if the kernel
> was compiled for SMP or not).
>
> Can you give a spin to this untested incremental fix?
[snip snip]
Yes, this does the trick for me. With this fix it survived the last 30m
of torture (consisting of make -j4 bzImage, a gcc build plus 2 mozillas
and 1 OpenOffice.org word processor, bear in mind it is only a P200 box)
blissfully -- previously it took only 15 seconds with a 1/3 that load to
lock up. So, this patch definitely cures it.
Nuno
next prev parent reply other threads:[~2002-12-02 0:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 11:54 Exaggerated swap usage Javier Marcet
2002-11-29 12:20 ` Christer Nilsson
2002-11-29 16:31 ` Rik van Riel
2002-11-30 1:38 ` Javier Marcet
2002-11-30 1:55 ` Rik van Riel
2002-11-30 2:47 ` Zwane Mwaikambo
2002-11-30 5:17 ` Javier Marcet
2002-11-30 14:02 ` Exaggerated swap usage && -aa lockup Javier Marcet
2002-11-30 2:42 ` Exaggerated swap usage Zwane Mwaikambo
2002-11-30 3:02 ` Andrew Morton
2002-11-30 4:12 ` Zwane Mwaikambo
2002-11-30 6:48 ` khromy
2002-11-30 6:49 ` Javier Marcet
2002-11-30 7:08 ` Dmitri
2002-11-30 14:05 ` Javier Marcet
2002-11-30 18:23 ` khromy
2002-11-30 18:43 ` Andrea Arcangeli
2002-12-01 7:39 ` Javier Marcet
2002-12-01 7:53 ` Javier Marcet
2002-12-01 10:34 ` Andrea Arcangeli
2002-12-01 7:59 ` Javier Marcet
2002-12-01 10:36 ` Andrea Arcangeli
2002-12-01 14:37 ` Nuno Monteiro
2002-12-02 0:21 ` Andrea Arcangeli
2002-12-02 1:01 ` Nuno Monteiro [this message]
2002-12-02 4:55 ` Javier Marcet
2002-12-02 21:24 ` Andrew Clayton
2002-11-30 14:05 ` Steffen Moser
2002-11-30 18:22 ` Rik van Riel
2002-12-01 7:57 ` Javier Marcet
2002-12-01 19:27 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2002-11-29 15:28 Randal, Phil
2002-11-29 16:28 ` Rik van Riel
2002-12-02 23:59 Marc-Christian Petersen
2002-12-03 0:59 ` Andrea Arcangeli
2002-12-03 10:13 ` Marc-Christian Petersen
2002-12-03 13:59 ` Andrea Arcangeli
2002-12-03 18:43 ` Marc-Christian Petersen
2002-12-05 23:14 ` Marc-Christian Petersen
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=20021202010144.GA728@hobbes.itsari.int \
--to=nuno@itsari.org \
--cc=andrea@suse.de \
--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