From: "Hua Zhong" <hzhong@gmail.com>
To: "'Dieter Stüken'" <stueken@conterra.de>, linux-kernel@vger.kernel.org
Subject: RE: ext3 metadata performace
Date: Thu, 11 May 2006 17:36:41 -0700 [thread overview]
Message-ID: <002501c6755c$24306430$493d010a@nuitysystems.com> (raw)
In-Reply-To: <4463461C.3070201@conterra.de>
> (3ware 9500S), which even has an battery buffered disk cache.
> Thus there is no need for synchronous IO anyway. If I disable
> the disk cache on my plain SATA disk using ext3, I also get
> this behavior.
If you mean the disk cache is reliable with the battery, then it should be done by the block layer that a write barrier doesn't
translate into a SYNC (or whatever it is called). Instead, data is considered synced to disk as soon as it hits the cache.
It's really nothing to do with EXT3. It's doing the right thing.
Hua
next prev parent reply other threads:[~2006-05-12 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 14:11 ext3 metadata performace Dieter Stüken
2006-05-11 15:43 ` Avi Kivity
2006-05-11 18:46 ` Miquel van Smoorenburg
2006-05-12 0:36 ` Hua Zhong [this message]
2006-05-12 6:35 ` Helge Hafting
2006-05-12 10:11 ` Dieter Stüken
[not found] <6bkbC-4V9-27@gated-at.bofh.it>
2006-05-12 0:12 ` Robert Hancock
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='002501c6755c$24306430$493d010a@nuitysystems.com' \
--to=hzhong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stueken@conterra.de \
/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