From: Ric Wheeler <rwheeler@redhat.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: async commit & write barrier code
Date: Mon, 22 Sep 2008 13:20:31 -0400 [thread overview]
Message-ID: <48D7D3DF.70505@redhat.com> (raw)
After today's call, I was poking around a bit to try and understand
better how the async commit code plays with the write barrier.
journal_submit_commit_record seems to disable the barriers when async IO
is enabled if I read the code correctly. If this is true, how can we
provide any promises of on disk data integrity after an fsync()?
Regards,
Ric
next reply other threads:[~2008-09-22 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 17:20 Ric Wheeler [this message]
2008-09-23 20:41 ` async commit & write barrier code Eric Sandeen
2008-09-23 22:35 ` Theodore Tso
2008-09-23 23:16 ` Ric Wheeler
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=48D7D3DF.70505@redhat.com \
--to=rwheeler@redhat.com \
--cc=linux-ext4@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 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.