From: Randy Dunlap <rdunlap@infradead.org>
To: Sergei Shtepa <sergei.shtepa@veeam.com>,
axboe@kernel.dk, hch@infradead.org, corbet@lwn.net,
snitzer@kernel.org
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, willy@infradead.org,
dlemoal@kernel.org, wsa@kernel.org,
heikki.krogerus@linux.intel.com, ming.lei@redhat.com,
gregkh@linuxfoundation.org, linux-block@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4 11/11] blksnap: Kconfig and Makefile
Date: Mon, 12 Jun 2023 16:43:09 -0700 [thread overview]
Message-ID: <499ded51-3fb8-f11b-8776-08ab2e9a8812@infradead.org> (raw)
In-Reply-To: <20230609115858.4737-11-sergei.shtepa@veeam.com>
On 6/9/23 04:58, Sergei Shtepa wrote:
> diff --git a/drivers/block/blksnap/Kconfig b/drivers/block/blksnap/Kconfig
> new file mode 100644
> index 000000000000..14081359847b
> --- /dev/null
> +++ b/drivers/block/blksnap/Kconfig
> @@ -0,0 +1,12 @@
> +# SPDX-License-Identifier: GPL-2.0
> +#
> +# Block device snapshot module configuration
> +#
> +
> +config BLKSNAP
> + tristate "Block Devices Snapshots Module (blksnap)"
> + help
> + Allow to create snapshots and track block changes for block devices.
> + Designed for creating backups for simple block devices. Snapshots are
> + temporary and are released then backup is completed. Change block
when backup is completed.
or is the order of operations as listed: release snapshots and then backup
can be completed?
> + tracking allows to create incremental or differential backups.
--
~Randy
next prev parent reply other threads:[~2023-06-12 23:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:58 [PATCH v4 01/11] documentation: Block Device Filtering Mechanism Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 02/11] block: " Sergei Shtepa
2023-06-13 1:51 ` Randy Dunlap
2023-06-13 12:34 ` Sergei Shtepa
2023-06-13 14:16 ` Randy Dunlap
2023-06-09 11:58 ` [PATCH v4 03/11] documentation: Block Devices Snapshots Module Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 04/11] blksnap: header file of the module interface Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 05/11] blksnap: module management interface functions Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 06/11] blksnap: handling and tracking I/O units Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 07/11] blksnap: minimum data storage unit of the original block device Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 08/11] blksnap: difference storage Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 09/11] blksnap: event queue from the " Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 10/11] blksnap: snapshot and snapshot image block device Sergei Shtepa
2023-06-09 11:58 ` [PATCH v4 11/11] blksnap: Kconfig and Makefile Sergei Shtepa
2023-06-12 23:43 ` Randy Dunlap [this message]
2023-06-13 10:47 ` Sergei Shtepa
2023-06-13 1:52 ` [PATCH v4 01/11] documentation: Block Device Filtering Mechanism Randy Dunlap
2023-06-13 15:23 ` Sergei Shtepa
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=499ded51-3fb8-f11b-8776-08ab2e9a8812@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dlemoal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=sergei.shtepa@veeam.com \
--cc=snitzer@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=wsa@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).