All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Haripriya S" <sharipriya@novell.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-snapshot scalability - chained delta snapshots approach
Date: Thu, 26 Oct 2006 02:29:07 -0600	[thread overview]
Message-ID: <4540C078.A648.00B6.0@novell.com> (raw)
In-Reply-To: <62b0912f0610231016r23585c34y6308cb3540ed926c@mail.gmail.com>

>>> "Molle Bestefich" <molle.bestefich@gmail.com> 10/23/06 10:46 PM >>>


> Complex, how?
> 
> Necessary operations (in order listed):
>  * Acquire exclusive lock on this snapshot.
>  * Check that next snapshot has room for exceptions, abort if not.

If the next snapshot in the write chain does not have
room, then we need to go through the list of earlier 
snapshots and move the exceptions to the first snapshot
which has room. This is because the earlier snapshots depend
on the data being copied in at least one of the later snapshots.
If the next snapshot is the earliest snapshot, then we can abort.

>  * Acquire exclusive lock on next snapshot.
>  * Move all exceptions to next snapshot.
>  * Unlock next snapshot.
>  * Remove this snapshot.
>  * Done...

Yes.

Thanks and Regards,
Haripriya

      parent reply	other threads:[~2006-10-26  8:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44DA246B020000B60000BD22@lucius.provo.novell.com>
     [not found] ` <44DB5BDD020000B60000BD96@lucius.provo.novell.com>
2006-08-10 10:46   ` snapshot scalability Haripriya S
2006-09-27  5:24     ` dm-snapshot scalability - chained delta snapshots approach Haripriya S
2006-09-27  9:17       ` Jan Blunck
2006-09-27 10:40         ` rgammans
2006-09-27 14:47           ` Bill Rugolsky Jr.
2006-10-23 17:16         ` Molle Bestefich
2006-10-24  9:52           ` Jan Blunck
2006-10-25 12:09             ` Haripriya S
2006-10-26  8:29           ` Haripriya S [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=4540C078.A648.00B6.0@novell.com \
    --to=sharipriya@novell.com \
    --cc=dm-devel@redhat.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.