public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Ricardo Galli <gallir@uib.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Report: 2.4.18 very high latencies (with lowlat. and pre-empt  patches)
Date: Thu, 04 Apr 2002 14:29:16 -0800	[thread overview]
Message-ID: <3CACD3BC.1EB55BCC@zip.com.au> (raw)
In-Reply-To: <E16tEL4-0006fr-00@antoli.gallimedina.net>

Ricardo Galli wrote:
> 
> Hi all (second try),
>         Linux becomes somehow unusable when I edited sound files and also
> during NFS copy. I've noticed the same effects also during i/o loads, for
> example when closing kmail after I deleted some messages.
> 

It would help if you could come up with a simple test case
which exhibits this problem - some sequence of steps which
is reproducible by others, and which has repeatable effects.

Is your I/O system performing properly?  Try running

	hdparm -t /dev/hdaX

where /dev/hdaX refers to your root filesystem.  You
should get 15-30 megabytes per second.

You also report that your PPC-based laptop has processes
unexpectedly terminating when the machine is under VM
pressure.  You should check your kernel logs (usually
/var/log/messages) to see if the process was killed
due to an out-of-memory condition.  If it's not that,
and if it's not due to application bugs then the ppc
kernel may be dropping modified- or dirty-bits in its
PTEs, which is rather unlikely.

-

  reply	other threads:[~2002-04-04 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 21:00 Report: 2.4.18 very high latencies (with lowlat. and pre-empt patches) Ricardo Galli
2002-04-04 22:29 ` Andrew Morton [this message]
2002-04-05 10:16   ` Ricardo Galli
2002-04-05 19:45     ` Andrew Morton
2002-04-05 19:58     ` Andrew Morton

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=3CACD3BC.1EB55BCC@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=gallir@uib.es \
    --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