From: Jens Axboe <axboe@suse.de>
To: Scott Lee <scottlee@redhot.rose.hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ide write barriers
Date: Wed, 26 Feb 2003 21:46:41 +0100 [thread overview]
Message-ID: <20030226204641.GJ945@suse.de> (raw)
In-Reply-To: <200302262031.MAA18505@redhot.rose.hp.com>
On Wed, Feb 26 2003, Scott Lee wrote:
> > The goal is to make the use of write
> > back cache enabled ide drives safe with journalled file systems.
>
> Does this mean that having write caching enabled is not safe if you
> are using ext3 on an IDE drive? Should "hdparm -W 0 /dev/hda" be used
> for example. (I see a 50% performance hit using "-W 0" when my box is
> under load.) If this is the case, what is the root cause? Do IDE
> drives reorder writes when they are cached?
As it stands, it's not safe to use write back caching on IDE drives.
When the write completes as seen from the fs, it's not on the platter
yet. That's a problem. And as you mention, there's no guarentee that
writes won't be reordered as well.
So yes, either use the barrier patch or disable write caching.
--
Jens Axboe
next prev parent reply other threads:[~2003-02-26 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 20:31 [PATCH] ide write barriers Scott Lee
2003-02-26 20:46 ` Jens Axboe [this message]
2003-02-27 21:57 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 21:20 LEE,SCOTT (HP-Roseville,ex1)
2003-02-26 23:10 ` Alan Cox
2003-02-05 15:18 Jens Axboe
2003-02-05 15:28 ` Marc-Christian Petersen
2003-02-05 16:33 ` Jens Axboe
2003-02-05 19:53 ` Marc-Christian Petersen
2003-02-06 9:26 ` Jens Axboe
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=20030226204641.GJ945@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=scottlee@redhot.rose.hp.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