All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jussi Laako <jussi.laako@kolumbus.fi>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Writeout in recent kernels/VMs poor compared to last -ac
Date: Sat, 12 Jan 2002 20:49:50 +0200	[thread overview]
Message-ID: <3C40854E.3EF132F3@kolumbus.fi> (raw)
In-Reply-To: <009e01c19b7c$463457d0$02c8a8c0@kroptech.com> <20020112173018.Q1482@inspiron.school.suse.de> <00fd01c19b95$b3ec3a40$02c8a8c0@kroptech.com>

Adam Kropelin wrote:
> 
> Thanks for the idea. Unfortunately, it didn't help. :(
> 
> Blocks definitely do begin hitting the disk much sooner after I begin the
> transfer, but the overall time is basically unchanged: 7:08. vmstat still 
> shows the widely oscillating bo value.

Here's what I get with 2.4.12-ac3-lowlatency (non-fixed X11 driver):
http://www.pp.song.fi/~visitor/latencytest/3x256.html

And here's 2.4.16-lowlatency (non-fixed X11 driver):
http://www.pp.song.fi/~visitor/latencytest2/3x256.html

Here's 2.4.16-lowlatency with some small patches (fixed X11 driver):
http://www.pp.song.fi/~visitor/latencytest3/3x256.html

Here's 2.4.17-ide-rmap-O1-minill (fixed X11 driver):
http://www.pp.song.fi/~visitor/latencytest4/3x256.html


So, only usable kernel is still 2.4.12-ac3 with fixed X11 driver.


 - Jussi Laako

-- 
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B  39DD A4DE 63EB C216 1E4B
Available at PGP keyservers


  reply	other threads:[~2002-01-12 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-12 15:17 Writeout in recent kernels/VMs poor compared to last -ac Adam Kropelin
2002-01-12 15:29 ` Adam Kropelin
2002-01-12 16:03 ` Rik van Riel
2002-01-12 16:30 ` Andrea Arcangeli
2002-01-12 18:19   ` Adam Kropelin
2002-01-12 18:49     ` Jussi Laako [this message]
2002-01-12 20:47 ` Jeff Lessem

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=3C40854E.3EF132F3@kolumbus.fi \
    --to=jussi.laako@kolumbus.fi \
    --cc=akropel1@rochester.rr.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.