mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi HOSHINO <hoshino@labs.cybozu.co.jp>
To: Ric Wheeler <rwheeler@redhat.com>,
	linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Takashi HOSHINO <hoshino@labs.cybozu.co.jp>
Subject: WalB: a wrapper block device driver for efficient backup and replication
Date: Mon, 03 Jun 2013 17:30:26 +0900	[thread overview]
Message-ID: <51AC5422.1080103@labs.cybozu.co.jp> (raw)

Hello,

I'm developing a wrapper block device driver called 'WalB'
that provides wrapper block devices to get consistent diff blocks
without full-scans of devices using Write-Ahead Logging technology,
in order to achieve incremental backup and asynchronous replication.

Its source code and documents are available in GitHub:
https://github.com/starpos/walb
https://github.com/starpos/walb/blob/develop/doc/index.creole

You can try it from now.
It supports kernel 3.2 to 3.9 and x86_64 architecture currently.

WalB achieves small overhead of IO response with:
- No persistent indexes.
- No undo-logs, just redo-logs.
- No block-level fragmentation.

I've talked about WalB at LinuxCon Japan 2013.
The slides in pdf are here:
http://www.slideshare.net/starpos/wal-b-linuxconjapan2013

At the conference, I asked Mr. Ric Wheeler what to do for the module to
be merged to the mainline kernel, and he suggested submitting an e-mail
ASAP.

WalB is provided as a single module currently.
It seems not so difficult to create 'drivers/block/walb' directory like
DRBD.
Is that nice idea? or do you have any comments?

Regards,

Takashi Hoshino

                 reply	other threads:[~2013-06-03  9:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51AC5422.1080103@labs.cybozu.co.jp \
    --to=hoshino@labs.cybozu.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rwheeler@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®