linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
	Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH v4 0/3] dioread_nolock patch
Date: Fri, 15 Jan 2010 14:39:48 -0500	[thread overview]
Message-ID: <4B50C484.3080902@redhat.com> (raw)
In-Reply-To: <1263583812-21355-1-git-send-email-tytso@mit.edu>

On 01/15/2010 02:30 PM, Theodore Ts'o wrote:
> I've worked with Jiaying to ready this patch for submission.
>
> It's currently a mount option for maximum safety, but after we do some
> benchmarking to make sure it doesn't degrade performance for buffered
> writes, we may want to make this the default.  Once really nice side
> effect of this patch is that it effectively gives us "guarded mode" by
> default, since the blocks are marked as uninitialized and only converted
> to be initialized when the I/O has completed for both buffered and
> direct I/O writes now.  This means that we could possibly change the
> default mode to be data=writeback if the extents feature is enabled,
> since data=ordered would only needed for safety when writing new
> old-style indirect blocks.
>
> The plan is to merge this for 2.6.34.  I've looked this over pretty
> carefully, but another pair of eyes would be appreciated, especially if
> we make this the default.  Beyond the advantages of being able to use
> data=writeback, I believe this should be a major win for database
> workloads.
>
> 					- Ted
>    

I would be really cautious about turning this on unless we are 100% 
certain that we have not introduced data integrity issues. Performance 
testing is great, but we need to work hard on the power failure testing, 
etc as well....

What ever did happen to guarded mode? Is it still lurking out there?

ric


> Theodore Ts'o (3):
>    ext4: mechanical change on dio get_block code in prepare for it to be
>      used by buffer write
>    ext4: use ext4_get_block_write in buffer write
>    ext4: Use direct_IO_no_locking in ext4 dio read.
>
>   fs/ext4/ext4.h      |   28 +++++---
>   fs/ext4/ext4_jbd2.h |   24 +++++++
>   fs/ext4/extents.c   |   36 +++++-----
>   fs/ext4/fsync.c     |    2 +-
>   fs/ext4/inode.c     |  192 +++++++++++++++++++++++++++++++++-----------------
>   fs/ext4/super.c     |   32 +++++++--
>   6 files changed, 217 insertions(+), 97 deletions(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>    


  parent reply	other threads:[~2010-01-15 19:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 19:30 [PATCH v4 0/3] dioread_nolock patch Theodore Ts'o
2010-01-15 19:30 ` [PATCH v4 1/3] ext4: mechanical change on dio get_block code in prepare for it to be used by buffer write Theodore Ts'o
2010-01-17 14:36   ` Aneesh Kumar K. V
2010-01-17 16:19     ` Eric Sandeen
2010-01-17 16:42       ` Aneesh Kumar K. V
2010-01-18  3:57       ` tytso
2010-01-15 19:30 ` [PATCH v4 2/3] ext4: use ext4_get_block_write in " Theodore Ts'o
2010-01-16  2:17   ` tytso
2010-01-17 14:21   ` Aneesh Kumar K. V
2010-01-18  5:25     ` Jiaying Zhang
2010-01-15 19:30 ` [PATCH v4 3/3] ext4: Use direct_IO_no_locking in ext4 dio read Theodore Ts'o
2010-01-17 14:19   ` Aneesh Kumar K. V
2010-01-15 19:39 ` Ric Wheeler [this message]
2010-01-15 19:52 ` [PATCH v4 0/3] dioread_nolock patch Eric Sandeen
2010-01-15 20:15   ` tytso
2010-01-15 20:17     ` Eric Sandeen
2010-01-15 21:47       ` Michael Rubin
2010-01-22 20:47         ` Valerie Aurora
2010-02-20  0:56           ` Michael Rubin
2010-02-23  0:36             ` Andreas Dilger
2010-02-16 21:07 ` Darrick J. Wong
2010-02-17 19:34   ` Jiaying Zhang
2010-02-19 21:25     ` Darrick J. Wong

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=4B50C484.3080902@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).