From: Vladimir Sementsov-Ogievskiy <firstname.lastname@example.org> To: email@example.com Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: [PATCH v2 for-6.2 0/6] push backup with fleecing Date: Wed, 4 Aug 2021 13:03:12 +0300 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Consider that as RFC. I'm preparing an alternative and more efficient fleecing scheme, based on special block driver, not on backing link. So, this will be rebased, and probably some permission-related difficulties may be avoided. 21.07.2021 17:04, Vladimir Sementsov-Ogievskiy wrote: > Hi all! > > Here is push-backup with fleecing. What is it: > > 1. Make fleecing scheme > > guest blk > | > |root > v > copy-before-write filter -------> temp qcow2 > | | > |file | backing > V | > active disk <------------------------- > > 2. Start backup job from temp qcow2 to final remote target (NBD or > something) > > Benefit in comparison with simple backup job: for remote final target > write operations are not very fast. And guest have to wait for > copy-before-write operations. With fleecing scheme target for > copy-before-write operations is local qcow2 file with faster access than > actual backup target. So, guest is less disturbed by copy-before-write > operations. > > Based-on: <firstname.lastname@example.org> > ([PATCH v6 00/33] block: publish backup-top filter) > > v2: > 01: changed to simply check s->target->perm > 06: make explicit immutable-source parameter instead of auto-detecting > > Vladimir Sementsov-Ogievskiy (6): > block/block-copy: use write-unchanged for fleecing scheme > block/copy-before-write: require BLK_PERM_WRITE_UNCHANGED for fleecing > block: share writes on backing child of fleecing node > block: blk_root(): return non-const pointer > qapi: backup: add immutable-source paramter > iotests/image-fleecing: test push backup with fleecing > > qapi/block-core.json | 12 ++- > block/copy-before-write.h | 1 + > include/block/block_int.h | 1 + > include/sysemu/block-backend.h | 2 +- > block.c | 3 +- > block/backup.c | 71 ++++++++++++- > block/block-backend.c | 2 +- > block/block-copy.c | 18 +++- > block/copy-before-write.c | 48 ++++++++- > block/replication.c | 2 +- > blockdev.c | 1 + > tests/qemu-iotests/tests/image-fleecing | 105 +++++++++++++++----- > tests/qemu-iotests/tests/image-fleecing.out | 61 ++++++++++++ > 13 files changed, 287 insertions(+), 40 deletions(-) > -- Best regards, Vladimir
prev parent reply other threads:[~2021-08-04 10:05 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-21 14:04 Vladimir Sementsov-Ogievskiy 2021-07-21 14:04 ` [PATCH v2 1/6] block/block-copy: use write-unchanged for fleecing scheme Vladimir Sementsov-Ogievskiy 2021-07-21 14:04 ` [PATCH v2 2/6] block/copy-before-write: require BLK_PERM_WRITE_UNCHANGED for fleecing Vladimir Sementsov-Ogievskiy 2021-07-21 14:04 ` [PATCH v2 3/6] block: share writes on backing child of fleecing node Vladimir Sementsov-Ogievskiy 2021-07-21 14:04 ` [PATCH v2 4/6] block: blk_root(): return non-const pointer Vladimir Sementsov-Ogievskiy 2021-07-21 14:04 ` [PATCH v2 5/6] qapi: backup: add immutable-source paramter Vladimir Sementsov-Ogievskiy 2021-07-21 14:04 ` [PATCH v2 6/6] iotests/image-fleecing: test push backup with fleecing Vladimir Sementsov-Ogievskiy 2021-08-04 10:03 ` Vladimir Sementsov-Ogievskiy [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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v2 for-6.2 0/6] push backup with fleecing' \ /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
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.