linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sage Weil <sage@newdream.net>
To: Goffredo Baroncelli <kreijack@libero.it>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] btrfs: implement 'async-snapshot' command
Date: Mon, 1 Nov 2010 09:29:22 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1011010921130.29194@cobra.newdream.net> (raw)
In-Reply-To: <201010302035.05962.kreijack@libero.it>

On Sat, 30 Oct 2010, Goffredo Baroncelli wrote:
> On Saturday, 30 October, 2010, Sage Weil wrote:
> > This is identical to 'snapshot', but uses the new async snapshot creation
> > ioctl, and prints out the transid the new snapshot will be committed
> > with.
> 
> Only for curiosity, how long may take snapshot a tree ? It should be only a 
> copy and update of few pages on the disk (the head of the trees), so the time 
> should be O(1)...

In theory, yes, but there is still a fair bit of disk io that goes on 
while preparing the commit in the current code.  Also, I found that even 
when the transaction does unblock, most operations end up waiting for the 
btree inode pages anyway, so there is definitely room for improvement.  
Still, this avoids waiting for the new superblocks to commit, and gets the 
interface in place to take advantage of future improvements in this area.

sage

  reply	other threads:[~2010-11-01 16:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 17:56 [PATCH 1/3] update ioctl.h from 2.6.37-rc1 Sage Weil
2010-10-30 17:56 ` [PATCH 2/3] btrfs: implement 'async-snapshot' command Sage Weil
2010-10-30 18:27   ` Goffredo Baroncelli
2010-11-01 16:31     ` Sage Weil
2010-11-02 18:42       ` Goffredo Baroncelli
2010-11-02 18:45         ` Sage Weil
2010-10-30 18:35   ` Goffredo Baroncelli
2010-11-01 16:29     ` Sage Weil [this message]
2010-10-30 17:56 ` [PATCH 3/3] btrfs: implement 'start-sync' and 'wait-sync' commands Sage Weil
2010-10-30 18:29   ` Goffredo Baroncelli

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=Pine.LNX.4.64.1011010921130.29194@cobra.newdream.net \
    --to=sage@newdream.net \
    --cc=kreijack@libero.it \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).