mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: akropel1@rochester.rr.com (Adam Kropelin)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18pre3-ac1
Date: Mon, 14 Jan 2002 00:47:54 +0000 (GMT)	[thread overview]
Message-ID: <E16PvI2-0008WI-00@the-village.bc.nu> (raw)
In-Reply-To: <028b01c19c90$87300760$02c8a8c0@kroptech.com> from "Adam Kropelin" at Jan 13, 2002 07:15:09 PM

> in the "Writeout in recent kernels..." thread) on this release. Performance and
> observed writeout behavior was essentially the same as for 2.4.17, both stock
> and with -rmap11a. Transfer time was 6:56 and writeout was uneven. 2.4.13-ac7 is
> still the winner by a significant margin.

That is very useful information actually. That does rather imply that some
of the performance hit came from the block I/O elevator differences in the
old ac tree (the ones Linus hated ;)). Now the question (and part of the
reason Linus didnt like them) - is why ?

Alan

  reply	other threads:[~2002-01-14  0:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 21:44 Alan Cox
2002-01-13 19:23 ` Thiago Rondon
2002-01-13 22:52 ` Ville Herva
2002-01-13 22:57   ` Alan Cox
2002-01-14  0:15 ` Adam Kropelin
2002-01-14  0:47   ` Alan Cox [this message]
2002-01-14  2:13     ` Benjamin LaHaise
2002-01-14  2:54   ` Rik van Riel
2002-01-14  5:47     ` Eric W. Biederman
2002-01-14  6:17       ` Rik van Riel
2002-01-14  7:25         ` Eric W. Biederman
2002-01-21  3:46           ` Daniel Phillips
2002-01-21  5:30           ` Richard Gooch
2002-01-21  5:34             ` Rik van Riel
2002-01-21  7:01               ` Eric W. Biederman
2002-01-21 12:02                 ` Rik van Riel
2002-01-21 14:02                 ` Daniel Phillips
2002-01-21 13:22             ` Daniel Phillips
2002-01-14  9:28         ` David S. Miller
2002-01-14 12:05           ` Rik van Riel

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=E16PvI2-0008WI-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®