All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Yan Zheng <zheng.yan@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] nodatacow fix
Date: Tue, 05 Aug 2008 10:19:50 -0400	[thread overview]
Message-ID: <1217945990.7611.72.camel@think.oraclecorp.com> (raw)
In-Reply-To: <48986070.9010900@oracle.com>

On Tue, 2008-08-05 at 22:15 +0800, Yan Zheng wrote:
> Hello,
> 
> This patch adapts nodatacow code for the new data ordered code. Ordered
> extents are used in all cases. It avoid writepage_start_hook kicking off
> nodatacow IO contiguously. This patch also makes btrfs wait for ordered
> extents before creating snapshots. It's important for nodatcow IO since
> creating snapshots invalidates the results of reference checking.
> 

Thanks Yan!  Can you please change this to make it only wait for
nodatacow ordered extents?

-chris



  reply	other threads:[~2008-08-05 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 14:15 [PATCH] nodatacow fix Yan Zheng
2008-08-05 14:19 ` Chris Mason [this message]
2008-08-05 16:50   ` Yan Zheng

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=1217945990.7611.72.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=zheng.yan@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.