From: <pcg@goof.com ( Marc) (A.) (Lehmann )>
To: Nicholas Knight <tegeran@home.com>
Cc: Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] Re: [PATCH] 2.4.10 improved reiserfs a lot, but could still be better
Date: Mon, 24 Sep 2001 18:40:08 +0200 [thread overview]
Message-ID: <20010924184008.A4126@schmorp.de> (raw)
In-Reply-To: <B0005839269@gollum.logi.net.au> <20010924173210.A7630@emma1.emma.line.org> <20010924161518.KYHD11251.femail27.sdc1.sfba.home.com@there>
In-Reply-To: <20010924161518.KYHD11251.femail27.sdc1.sfba.home.com@there>
On Mon, Sep 24, 2001 at 09:15:19AM -0700, Nicholas Knight <tegeran@home.com> wrote:
[turning off write-cache]
> I'm sorry, but that's not acceptable.
(I had it turned off for a long time, until I reasoned: real power-outages
are very rare, so I can leave it turned on anyways and risk a
filesystemcheck after outages).
The reason this kills performance ALWAYS is that ide does not support large
enough transfer sizes (8-32k on most drives) to fill one track.
Turning off write caching has a big chance of lowering your transaction
throughput to the drive's RPM. Combined with linux' not-that-optimal elevator
and write behaviour this has good chances of costing a lot of performance.
TCQ will obviously help, but I somehow doubt it will work fine - even with
SCSI TCQ is a nightmare (the aic7xxx drive regularly kills my system if
tagged queueing is enabled for example). IDE currently is a mess (I do
_not_ expect my drive performance to simply halve just because two devices
to share the bus, even if this is how conservative ide is destined to
work).
I am convinced that there is a way of creating a hard write barrier (e.g.
a cache flush that waits) with most if not all ide disks - putting them
into powersave should work, if nothing else ;)
So apart from driver issues (such as TCQ), the mid-layer needs to be improved
(and plans already exist) to support semi-ordered writes and give as much
control over the device cache as possible.
Not to mention that the VM needs improvements here as well.
I didn't say much more than Alan implied: we have to live with it, so we
better think about making it work.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next prev parent reply other threads:[~2001-09-24 16:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 14:09 [PATCH] 2.4.10 improved reiserfs a lot, but could still be better Beau Kuiper
2001-09-24 14:46 ` [reiserfs-list] " Chris Mason
2001-09-24 15:32 ` Matthias Andree
2001-09-24 15:45 ` Alan Cox
2001-09-24 15:47 ` Matthias Andree
2001-09-24 16:08 ` Alan Cox
2001-09-24 16:08 ` [reiserfs-list] " Chris Dukes
2001-09-24 16:54 ` Matthias Andree
2001-09-24 16:15 ` Nicholas Knight
2001-09-24 16:40 ` Lehmann [this message]
2001-09-24 16:53 ` Matthias Andree
2001-09-24 16:57 ` [reiserfs-list] " Lehmann
2001-09-25 14:04 ` bill davidsen
2001-09-25 17:39 ` bill davidsen
2001-09-24 20:05 ` Nicholas Knight
2001-09-25 0:11 ` Matthias Andree
2001-09-25 4:49 ` Nicholas Knight
2001-09-25 6:00 ` Beau Kuiper
2001-09-25 6:17 ` Nicholas Knight
2001-09-25 10:44 ` Matthias Andree
2001-09-25 11:01 ` ben-lists
2001-09-25 10:42 ` Matthias Andree
2001-09-25 11:07 ` Nicholas Knight
2001-09-25 14:47 ` Alex Bligh - linux-kernel
2001-09-25 15:13 ` Matthias Andree
2001-09-25 15:23 ` John Alvord
2001-09-25 22:41 ` bill davidsen
2001-09-25 12:54 ` Jorge Nerín
2001-09-25 13:06 ` [reiserfs-list] " Chris Mason
2001-09-25 13:17 ` Matthias Andree
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=20010924184008.A4126@schmorp.de \
--to=pcg@goof.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
--cc=reiserfs-list@namesys.com \
--cc=tegeran@home.com \
/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