All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: device-mapper development <dm-devel@redhat.com>
Cc: Mike Snitzer <msnitzer@redhat.com>, Alasdair G Kergon <agk@redhat.com>
Subject: Re: Shared snapshots
Date: Thu, 7 Jan 2010 10:42:55 +0200	[thread overview]
Message-ID: <20100107084255.GP25902@reaktio.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1001060927120.28095@hs20-bc2-1.build.redhat.com>

On Wed, Jan 06, 2010 at 09:38:00AM -0500, Mikulas Patocka wrote:
> Hi
> 
> I uploaded new code for shared snapshots at
> http://people.redhat.com/mpatocka/patches/kernel/new-snapshots/devel/
> 
> Changes:
> - two queues, one for reads and one for writes, to improve read latency 
> when the device is write-congested
> - limit number of reallocations in flight (VM subsystem sends all writes 
> at once and without limit it creates big lags).
> - fixed one place where it didn't handle on-disk errors
> - simplified bitmap creation, removed some unneeded code
> - new macro for error reporting, as suggested by Zdenek
> - some comments added
> - DM_ prefix added to some macros
> 
> Userspace for lvm 2.02.53 is at
> http://people.redhat.com/mpatocka/patches/userspace/new-snapshots/lvm-2.02.54/
> 
> Please, someone, do offensive testing with this --- i.e. apply the 
> patches, try it, and try all possible lvm commands with it, try to stress 
> and crash it in various ways, etc. If we wait with testing until Alasdair 
> reads the code, it won't get much testing...
> 

Sorry for a stupid question, but what does "shared" mean? Support for CLVM?

-- Pasi

  reply	other threads:[~2010-01-07  8:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 14:38 Shared snapshots Mikulas Patocka
2010-01-07  8:42 ` Pasi Kärkkäinen [this message]
2010-01-07  9:05   ` haad
2010-01-07 10:08     ` 张宇
2010-01-11  9:14       ` Mikulas Patocka
2010-01-11  9:12   ` Mikulas Patocka
2010-01-11  9:40     ` Pasi Kärkkäinen
2010-01-11  9:49       ` Mikulas Patocka
  -- strict thread matches above, loose matches on Subject: below --
2010-09-10 17:47 shared snapshots Mikulas Patocka
2009-12-16  8:05 Shared snapshots Mikulas Patocka
2009-12-16 20:39 ` Mike Snitzer
2009-12-17 16:32   ` Mike Snitzer
2010-03-30 16:26   ` Mike Snitzer
2010-03-31  3:43     ` Mikulas Patocka
2009-12-22  9:50 ` 张宇
     [not found] <1240610034.7392.284.camel@p670.boston.redhat.com>
     [not found] ` <Pine.LNX.4.64.0904270815420.18227@hs20-bc2-1.build.redhat.com>
     [not found]   ` <1240836879.1759.16.camel@p670.boston.redhat.com>
     [not found]     ` <Pine.LNX.4.64.0905040741190.20446@hs20-bc2-1.build.redhat.com>
     [not found]       ` <15B46C78-2846-43C4-8090-1EC362E24FD7@redhat.com>
2009-05-06 16:06         ` Mikulas Patocka
2009-05-07 15:44           ` Jonathan Brassow
2009-05-11 10:44             ` Mikulas Patocka
2009-02-03  6:25 shared snapshots Mikulas Patocka
2009-02-03  6:48 ` FUJITA Tomonori
2009-02-05 22:17   ` Jonathan Brassow
2009-02-06  7:18     ` FUJITA Tomonori
2009-02-20 23:58       ` Jonathan Brassow
2009-02-06  3:44   ` Mikulas Patocka

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=20100107084255.GP25902@reaktio.net \
    --to=pasik@iki.fi \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=msnitzer@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.