From: Muthian Sivathanu <muthian_s@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: ext3 journal commit performance
Date: Wed, 2 Mar 2005 08:58:14 -0800 (PST) [thread overview]
Message-ID: <20050302165814.70651.qmail@web53704.mail.yahoo.com> (raw)
Hi,
I have a question on ext3 journal commit code. When a
transaction is committed in the ordered mode, ext3
first issues the data writes, waits for them to
finish, then issues the journal writes, waits for them
to finish, and then writes out the commit record.
It appears that the first wait (for the data blocks)
is unnecessary because all that is required is that
before the commit, both the data and the metadata
blocks should be on disk. This extra wait can
potentially reduce performance in cases where the
journal is on a separate disk, because you lose
parallelism between data writes and the metadata
writes.
Does anyone have an idea as to why this extra wait was
introduced?
thanks very much,
Muthian
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next reply other threads:[~2005-03-02 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 16:58 Muthian Sivathanu [this message]
2005-03-02 17:41 ` ext3 journal commit performance linux-os
2005-03-02 17:46 ` Muthian Sivathanu
2005-03-02 17:58 ` Andrew Morton
2005-03-02 21:29 ` Andrew Morton
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=20050302165814.70651.qmail@web53704.mail.yahoo.com \
--to=muthian_s@yahoo.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