From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com,
kwolf@redhat.com, berto@igalia.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v2 0/8] qcow2: encryption threads
Date: Tue, 11 Dec 2018 16:50:33 +0000 [thread overview]
Message-ID: <20181211165033.GQ921@redhat.com> (raw)
In-Reply-To: <20181211164317.32893-1-vsementsov@virtuozzo.com>
On Tue, Dec 11, 2018 at 07:43:09PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> The series brings threads to qcow2 encryption/decryption path,
> like it is already done for compression.
>
> v2: - multiple cipher inside QCryptoBlock instead of multiple
> blocks inside qcow2, as suggested by Daniel, and it is
> done in separate series
> - use threaded encryption in do_perform_cow_encrypt() too
> - some renaming and refactoring and simplifications
> (Sorry for not being very careful about change list, but v1 isn't
> actually reviewed, as approach with multiple blocks was early
> rejected by Denial)
>
> The series now based on two queued for 4.0 series, which, in
> turn, may be applied in any order: "crypto threads" (Daniel's
> tree), and "qcow2 decompress in threads", which is now in
> Kevin's block-next.
FYI I've pushed my crypto queue here for benefit of anyone
wishing to test this series
https://github.com/berrange/qemu/tree/qcrypto-next
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-12-11 16:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 16:43 [Qemu-devel] [PATCH v2 0/8] qcow2: encryption threads Vladimir Sementsov-Ogievskiy
2018-12-11 16:43 ` [Qemu-devel] [PATCH v2 1/8] qcow2.h: add missing include Vladimir Sementsov-Ogievskiy
2018-12-13 10:18 ` Alberto Garcia
2018-12-11 16:43 ` [Qemu-devel] [PATCH v2 2/8] qcow2: add separate file for threaded data processing functions Vladimir Sementsov-Ogievskiy
2019-01-03 15:11 ` Alberto Garcia
2018-12-11 16:43 ` [Qemu-devel] [PATCH v2 3/8] qcow2-threads: use thread_pool_submit_co Vladimir Sementsov-Ogievskiy
2019-01-03 15:28 ` Alberto Garcia
2018-12-11 16:43 ` [Qemu-devel] [PATCH v2 4/8] qcow2-threads: split out generic path Vladimir Sementsov-Ogievskiy
2018-12-13 23:28 ` Paolo Bonzini
2018-12-14 8:51 ` Vladimir Sementsov-Ogievskiy
2019-01-04 14:59 ` Alberto Garcia
2018-12-11 16:43 ` [Qemu-devel] [PATCH v2 5/8] qcow2: qcow2_co_preadv: improve locking Vladimir Sementsov-Ogievskiy
2018-12-11 16:43 ` [Qemu-devel] [PATCH v2 6/8] qcow2: qcow2_co_preadv: skip using hd_qiov when possible Vladimir Sementsov-Ogievskiy
2018-12-11 16:43 ` [Qemu-devel] [PATCH v2 7/8] qcow2: bdrv_co_pwritev: move encryption code out of the lock Vladimir Sementsov-Ogievskiy
2018-12-11 16:43 ` [Qemu-devel] [PATCH v2 8/8] qcow2: do encryption in threads Vladimir Sementsov-Ogievskiy
2018-12-11 16:50 ` Daniel P. Berrangé [this message]
2018-12-17 13:53 ` [Qemu-devel] [PATCH v2 0/8] qcow2: encryption threads Vladimir Sementsov-Ogievskiy
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=20181211165033.GQ921@redhat.com \
--to=berrange@redhat.com \
--cc=berto@igalia.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).