All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 0/5] crypto threads
Date: Mon, 10 Dec 2018 15:19:19 +0000	[thread overview]
Message-ID: <20181210151918.GO20272@redhat.com> (raw)
In-Reply-To: <20181207161351.4380-1-vsementsov@virtuozzo.com>

On Fri, Dec 07, 2018 at 07:13:46PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all.
> 
> v3:
> 01: add r-b by Daniel and Alberto
> 02: Alberto r-b
>     encrypt->encdec for generic
> 03: qcrypto_cipher_*crypt_helper->
>     qcrypto_block_cipher_*crypt_helper
> 04: rebased on previous renamings
>     Daniel r-b
> 05: use size_t
>     improve comment about n_threads
>     don't use ret in qcrypto_block_luks_create
>     do qemu_mutex_init at the end of open/create
>     do qemu_mutex_destroy in free
>     fix comment for qcrypto_block_get_cipher
> 
> v2:
> 05: fix compilation of test-crypto-block (I am ashamed:(
>     and change QCryptoBlock interface to be a bit more safe.
> 
> These series are preliminary step before moving encryption code in
> qcow2 to the threads. The first attempt of doing it is on list
> ([PATCH 00/11] qcow2: encryption threads : 
>  https://lists.gnu.org/archive/html/qemu-block/2018-11/msg00729.html)
> But it's approach with multiplying the whole QCryptoBlock per thread
> was rejected. So, here is a solution to maintain multitasking inside
> QCryptoBlock.

Thanks, I've queued this series for when 4.0 opens up.

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 :|

      parent reply	other threads:[~2018-12-10 15:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 16:13 [Qemu-devel] [PATCH v3 0/5] crypto threads Vladimir Sementsov-Ogievskiy
2018-12-07 16:13 ` [Qemu-devel] [PATCH v3 1/5] crypto/block-luks: fix memory leak in qcrypto_block_luks_create Vladimir Sementsov-Ogievskiy
2018-12-07 16:13 ` [Qemu-devel] [PATCH v3 2/5] crypto/block: refactor qcrypto_block_*crypt_helper functions Vladimir Sementsov-Ogievskiy
2018-12-07 16:13 ` [Qemu-devel] [PATCH v3 3/5] crypto/block: rename qcrypto_block_*crypt_helper Vladimir Sementsov-Ogievskiy
2018-12-10 10:44   ` Alberto Garcia
2018-12-10 13:21     ` Daniel P. Berrangé
2018-12-10 13:24       ` Alberto Garcia
2018-12-07 16:13 ` [Qemu-devel] [PATCH v3 4/5] crypto/block: introduce qcrypto_block_*crypt_helper functions Vladimir Sementsov-Ogievskiy
2018-12-10 10:45   ` Alberto Garcia
2018-12-07 16:13 ` [Qemu-devel] [PATCH v3 5/5] crypto: support multiple threads accessing one QCryptoBlock Vladimir Sementsov-Ogievskiy
2018-12-10 14:06   ` Alberto Garcia
2018-12-10 14:52     ` Daniel P. Berrangé
2018-12-10 15:09       ` Alberto Garcia
2018-12-10 15:16         ` Daniel P. Berrangé
2018-12-10 15:24           ` Alberto Garcia
2018-12-10 15:19 ` Daniel P. Berrangé [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 \
    --in-reply-to=20181210151918.GO20272@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 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.