From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>,
Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 0/5] Improve I/O tests coverage of LUKS
Date: Tue, 9 May 2017 17:18:56 +0200 [thread overview]
Message-ID: <20170509151856.GH5243@noname.str.redhat.com> (raw)
In-Reply-To: <20170502155452.7033-1-berrange@redhat.com>
Am 02.05.2017 um 17:54 hat Daniel P. Berrange geschrieben:
> The main goal of this series is to get the I/O tests passing
> 100% with LUKS when run with './check -luks'. It also adds a
> few more combinations to the LUKS/dmcrypt interoperability
> test.
>
> To make LUKS testing not quite as slow, we drop the PBKDF
> iteration count down to a very small value. This doesn't
> remove all overhead, as formatting the volume will always
> measure PBKDF timing over a 1 second interval.
It looks like patch 2 needs a rebase before it can be applied to my
block branch.
Kevin
prev parent reply other threads:[~2017-05-09 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 15:54 [Qemu-devel] [PATCH v4 0/5] Improve I/O tests coverage of LUKS Daniel P. Berrange
2017-05-02 15:54 ` [Qemu-devel] [PATCH v4 1/5] iotests: skip 159 & 170 with luks format Daniel P. Berrange
2017-05-02 15:54 ` [Qemu-devel] [PATCH v4 2/5] iotests: fix remainining tests to work with LUKS Daniel P. Berrange
2017-05-02 15:54 ` [Qemu-devel] [PATCH v4 3/5] iotests: reduce PBKDF iterations when testing LUKS Daniel P. Berrange
2017-05-02 15:54 ` [Qemu-devel] [PATCH v4 4/5] iotests: add more LUKS hash combination tests Daniel P. Berrange
2017-05-02 15:54 ` [Qemu-devel] [PATCH v4 5/5] iotests: chown LUKS device before qemu-io launches Daniel P. Berrange
2017-05-09 15:18 ` Kevin Wolf [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=20170509151856.GH5243@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).