From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] OCFS2: fdatasync should skip unimportant metadata writeout
Date: Tue, 9 Jun 2009 11:01:02 -0700 [thread overview]
Message-ID: <20090609180102.GA30966@mail.oracle.com> (raw)
In-Reply-To: <6.0.0.20.2.20090609154314.0729f488@172.19.0.2>
On Tue, Jun 09, 2009 at 04:47:45PM +0900, Hisashi Hifumi wrote:
> In ocfs2, fdatasync and fsync are identical.
> I think fdatasync should skip committing transaction when
> inode->i_state is set just I_DIRTY_SYNC and this indicates
> only atime or/and mtime updates.
> Following patch improves fdatasync throughput.
Nicely done, thanks. This is now in the ocfs2 git tree.
Joel
--
"Always give your best, never get discouraged, never be petty; always
remember, others may hate you. Those who hate you don't win unless
you hate them. And then you destroy yourself."
- Richard M. Nixon
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2009-06-09 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 7:52 [Ocfs2-devel] [PATCH] OCFS2: fdatasync should skip unimportant metadata writeout Hisashi Hifumi
2009-06-09 17:36 ` Mark Fasheh
2009-06-09 18:01 ` Joel Becker [this message]
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=20090609180102.GA30966@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.