From: Daniel Phillips <phillips@arcor.de>
To: Kevin Corry <kevcorry@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Andreas Dilger <adilger@clusterfs.com>,
Alasdair G Kergon <agk@redhat.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] 2/5: Device-mapper: kcopyd
Date: Sat, 3 Jul 2004 01:44:44 -0400 [thread overview]
Message-ID: <200407030144.44857.phillips@arcor.de> (raw)
In-Reply-To: <200406021150.48049.kevcorry@us.ibm.com>
On Wednesday 02 June 2004 12:50, Kevin Corry wrote:
> On Wednesday 02 June 2004 11:15 am, Andreas Dilger wrote:
> > It might be nice to have a brief comment here explaining what this is
> > and how it is supposed to be used.
>
> How's this?
>
> We're also working on some general documentation which will go in
> Documentation/device-mapper and will include more detailed information
> about the core driver and the other sub-modules. We'll try to submit those
> patches in the near future.
>
> + * Kcopyd provides a simple interface for copying an area of one
> + * block-device to one or more other block-devices, with an asynchronous
> + * completion notification.
Hi Kevin,
Once again, sorry for the lag.
Since not everybody knows the device-mapper code by heart, I'll add that
kcopyd is used by the snapshot target to perform copyouts, that is, to
preserve snapshotted data that would otherwise be overwritten.
Another potential use would be synching in the mirror target.
Regards,
Daniel
next prev parent reply other threads:[~2004-07-03 5:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 15:41 [PATCH] 2/5: Device-mapper: kcopyd Alasdair G Kergon
2004-06-02 16:15 ` Andreas Dilger
2004-06-02 16:50 ` Kevin Corry
2004-07-03 5:44 ` Daniel Phillips [this message]
2004-06-02 21:15 ` Alasdair G Kergon
2004-06-03 3:41 ` Andrew Morton
2004-06-03 13:28 ` Alasdair G Kergon
2004-06-10 6:18 ` Andrew Morton
2004-06-10 8:16 ` Kevin Corry
2004-06-10 18:12 ` Andrew Morton
2004-06-10 14:55 ` Alasdair G Kergon
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=200407030144.44857.phillips@arcor.de \
--to=phillips@arcor.de \
--cc=adilger@clusterfs.com \
--cc=agk@redhat.com \
--cc=akpm@osdl.org \
--cc=kevcorry@us.ibm.com \
--cc=linux-kernel@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