public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: war <war@starband.net>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is it normal for freezing while...
Date: Sat, 01 Dec 2001 00:52:36 -0500	[thread overview]
Message-ID: <3C087023.9683B8AF@starband.net> (raw)
In-Reply-To: <3C085B04.50ABE0B5@starband.net> <3C0867A3.5119D2BC@zip.com.au>

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

Wow, responsiveness is wonderful with these patches.

Will they make it into 2.4.17, (ie: I've seen the -pre2 changelog, did
you incorporate them into -pre2)?
Even throughout the entire dd, it remained responsive
(mouse/cursor/network/etc).

Attached is the vmstat log during the dd.


Andrew Morton wrote:

> war wrote:
> >
> > Is it normal for a system to lockup while creating a 3GB test file?
> >
>
> Seems that way.
>
> It also seems that yesterday I sent you the URL of two patches:
>
> http://www.zip.com.au/~akpm/linux/2.4/2.4.17-pre1/vm-fixes.patch
> http://www.zip.com.au/~akpm/linux/2.4/2.4.17-pre1/elevator.patch
>
> and I explicitly asked you to report on the result of applying them?
>
> If you apply them, you'll find that the problem goes away. If you're
> using ext3, you'll get better results if you mount with the `noatime'
> option.
>
> So please - test the patches, report the results.  It's how things
> work around here.  Sometimes :)
>
> Thanks.
>
> -

[-- Attachment #2: vmstat.log.bz2 --]
[-- Type: application/octet-stream, Size: 4020 bytes --]

  reply	other threads:[~2001-12-01  5:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01  4:22 Is it normal for freezing while war
2001-12-01  5:16 ` Andrew Morton
2001-12-01  5:52   ` war [this message]
2001-12-01  6:16     ` Andrew Morton
2001-12-01  8:15       ` Mike Galbraith
2001-12-01  8:26       ` Mike Fedyk
2001-12-01  9:02         ` Mike Fedyk

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=3C087023.9683B8AF@starband.net \
    --to=war@starband.net \
    --cc=akpm@zip.com.au \
    --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