From: Steve Lion <s.lion@verizon.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Unresponiveness of 2.4.16
Date: Mon, 26 Nov 2001 19:05:08 -0500 [thread overview]
Message-ID: <20011126190508.A23249@verizon.net> (raw)
In-Reply-To: <E168U3m-00077F-00@the-village.bc.nu> <Pine.LNX.4.33.0111261825340.15932-100000@xanadu.home>
In-Reply-To: <Pine.LNX.4.33.0111261825340.15932-100000@xanadu.home>; from nico@cam.org on Mon, Nov 26, 2001 at 06:34:26PM -0500
I'm running 2.4.13-ac7 with preempt patch and ext3 on this box. I don't seem
to be encountering any unresponsiveness at all while untar'ing a kernel src.
Just some info for you guys.
-Steve
* Nicolas Pitre (nico@cam.org) wrote:
> On Mon, 26 Nov 2001, Alan Cox wrote:
>
> > > 2.4.16 becomes very unresponsive for 30 seconds or so at a time during
> > > large unarchiving of tarballs, like tar -zxf mozilla-src.tar.gz. The
> > > file is about 36mb. I run top in one window, run free repeatedly in
> >
> > This seems to be one of the small as yet unresolved problems with the newer
> > VM code in 2.4.16. I've not managed to prove its the VM or the differing
> > I/O scheduling rules however.
>
> FWIW...
>
> I experienced quite the same unresponsiveness but more in the order of 4-5
> seconds since I started to use ext3 with RH 7.2 (i.e. kernel 2.4.7 based).
> I'm currently running 2.4.15-pre7 and the same momentary stalls are there
> just like with 2.4.7. It is much more visible when applying large patches to
> a kernel source tree as the patch output stops scrolling from time to time
> for about 5 secs. I never saw such thing while previously using reiserfs.
> I've yet to try reiserfs on a 2.4.16 tree to see if this is actually an ext3
> problem.
>
>
> Nicolas
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-11-27 0:02 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 22:02 Unresponiveness of 2.4.16 Nathan G. Grennan
2001-11-26 22:17 ` Alan Cox
2001-11-26 23:34 ` Nicolas Pitre
2001-11-27 0:05 ` Steve Lion [this message]
2001-11-27 9:12 ` Ahmed Masud
2001-11-27 17:12 ` Andrew Morton
2001-11-27 20:31 ` Mike Fedyk
2001-11-27 20:57 ` Andrew Morton
2001-11-27 21:19 ` Martin Eriksson
2001-11-27 21:24 ` Mike Fedyk
2001-11-28 18:24 ` Marcelo Tosatti
2001-11-28 18:57 ` Marcelo Tosatti
2001-11-28 20:31 ` Andrew Morton
2001-11-28 20:56 ` Andreas Dilger
2001-11-28 21:12 ` Andrew Morton
2001-11-28 20:04 ` Marcelo Tosatti
2001-11-28 21:26 ` Andrew Morton
2001-11-26 23:59 ` Rik van Riel
2001-11-27 0:36 ` Andrew Morton
2001-11-27 0:46 ` Rik van Riel
2001-11-27 4:38 ` Mike Fedyk
2001-11-27 4:45 ` Andrew Morton
2001-11-27 1:45 ` Andrea Arcangeli
2001-11-26 22:21 ` Andrew Morton
2001-11-27 7:42 ` Jens Axboe
2001-11-27 7:58 ` Mike Fedyk
2001-11-27 8:01 ` Jens Axboe
2001-11-27 8:31 ` Andrew Morton
2001-11-27 8:38 ` Jens Axboe
2001-11-26 22:44 ` Lincoln Dale
2001-11-27 4:34 ` GOTO Masanori
2001-11-27 0:44 ` Lost Logic
2001-11-27 0:57 ` Lost Logic
2001-11-27 3:49 ` Sean Elble
2001-11-27 3:56 ` Doug Ledford
2001-11-27 4:00 ` Sean Elble
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 9:56 willy tarreau
2001-11-27 10:57 ` Heinz Diehl
2001-11-28 0:33 Torrey Hoffman
2001-11-28 0:48 ` Andrew Morton
2001-11-28 18:09 ` Marcelo Tosatti
2001-11-28 19:38 ` Andrew Morton
2001-11-28 1:31 Dieter Nützel
2001-11-28 2:13 ` Andrew Morton
2001-11-28 2:34 ` Mike Fedyk
2001-11-28 2:48 ` Andrew Morton
2001-11-28 20:21 ` Roger Larsson
2001-11-28 3:53 ` Dieter Nützel
[not found] ` <200111280353.fAS3rEB05638@zero.tech9.net>
2001-11-28 4:14 ` Robert Love
2001-11-28 18:56 Torrey Hoffman
2001-11-28 19:31 ` Andrew Morton
2001-11-28 19:42 Torrey Hoffman
2001-11-28 20:51 ` Dieter Nützel
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=20011126190508.A23249@verizon.net \
--to=s.lion@verizon.net \
--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