All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@digeo.com>
Cc: rwhron@earthlink.net, linux-kernel@vger.kernel.org,
	lse-tech@lists.sourceforge.net
Subject: Re: big ext3 sequential write improvement in 2.5.51-mm1 gone in 2.5.53-mm1
Date: Sat, 25 Jan 2003 02:54:56 +1100	[thread overview]
Message-ID: <3E3161D0.1060403@cyberone.com.au> (raw)
In-Reply-To: 20030123231117.29c8eb98.akpm@digeo.com

Andrew Morton wrote:

>rwhron@earthlink.net wrote:
>
>>qsbench creates heavy swap load and simultaneous ed build. (small gnu package 
>>"tar xzf/configure/make/make check").
>>
>
>[snip]
>(Well, 2.5 _used_ to run it faster.  The anticipatory scheduling patch makes
>2.5's qsbench a little slower than 2.4.  `qsbench -m 350' on `mem=256m').
>
Some regressions are probably unavoidable, however a lot should be
able to be tuned out.

Nick


      reply	other threads:[~2003-01-24 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24  4:41 big ext3 sequential write improvement in 2.5.51-mm1 gone in 2.5.53-mm1 rwhron
2003-01-24  7:11 ` Andrew Morton
2003-01-24 15:54   ` Nick Piggin [this message]

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=3E3161D0.1060403@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=rwhron@earthlink.net \
    /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.