From: Mark Brown <broonie@kernel.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Mike Snitzer <snitzer@redhat.com>,
axboe@kernel.dk, Alasdair G Kergon <agk@redhat.com>,
dm-devel@redhat.com, neilb@suse.com, linux-raid@vger.kernel.org,
jack@suse.cz, Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>,
keith.busch@intel.com, jmoyer@redhat.com, tj@kernel.org,
bart.vanassche@sandisk.com, "Garg, Dinesh" <dineshg@quicinc.com>
Subject: Re: [PATCH 0/2] Introduce the request handling for dm-crypt
Date: Thu, 12 Nov 2015 10:04:22 +0000 [thread overview]
Message-ID: <20151112100422.GM12392@sirena.org.uk> (raw)
In-Reply-To: <CAMz4kuKNAkFG4-f6TU1HRxgkAn+YX-D_tTQAWio-A_np3brr+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
On Thu, Nov 12, 2015 at 04:20:41PM +0800, Baolin Wang wrote:
> 3. perforamence data
> It is just a simple dd test result, and will provide the formal report
> in future. But from the simple test, we can see the improvement.
It's probably also worth pointing out that Qualcomm have been shipping
an out of tree implementation of this as a separate module in their BSP
(originally written by Danesh Garg who's on this thread):
https://android.googlesource.com/kernel/msm/+/android-msm-dory-3.10-kitkat-wear/drivers/md/dm-req-crypt.c
Android now wants to encrypt phones and tablets by default and have been
seeing substantial performance hits as a result, we can try to get
people to share performance data from productionish systems but it might
be difficult.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-11-12 10:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 9:31 [PATCH 0/2] Introduce the request handling for dm-crypt Baolin Wang
2015-11-11 9:31 ` [PATCH 1/2] block: Introduce BIO_ENDIO_FREE for bio flags Baolin Wang
2015-11-11 17:54 ` Mike Snitzer
2015-11-12 4:05 ` Baolin Wang
2015-11-11 9:31 ` [PATCH 2/2] md: dm-crypt: Introduce the request handling for dm-crypt Baolin Wang
2015-11-11 9:48 ` [PATCH 0/2] " Christoph Hellwig
2015-11-12 2:15 ` Baolin Wang
2015-11-12 9:17 ` Jan Kara
2015-11-12 9:40 ` Baolin Wang
2015-11-12 11:06 ` Jan Kara
2015-11-12 11:46 ` Baolin Wang
2015-11-12 12:24 ` Jan Kara
2015-11-12 12:51 ` Baolin Wang
2015-11-12 12:57 ` Arnd Bergmann
2015-11-12 15:02 ` Mark Brown
2015-11-13 3:27 ` Baolin Wang
2015-11-13 3:25 ` Baolin Wang
2015-11-12 12:59 ` Jan Kara
2015-11-13 2:05 ` Baolin Wang
2015-11-13 9:05 ` Arnd Bergmann
2015-11-13 11:37 ` Baolin Wang
2015-11-11 18:18 ` Mike Snitzer
2015-11-12 2:36 ` Baolin Wang
2015-11-12 9:06 ` [dm-devel] " Christoph Hellwig
2015-11-12 8:20 ` Baolin Wang
2015-11-12 10:04 ` Mark Brown [this message]
2015-11-12 15:26 ` Jens Axboe
2015-11-13 2:07 ` Baolin Wang
2015-11-13 11:51 ` Mark Brown
2015-12-02 12:46 ` Baolin Wang
2015-12-02 19:56 ` [dm-devel] " Alasdair G Kergon
2015-12-03 2:56 ` Baolin Wang
2015-12-03 10:36 ` Baolin Wang
2015-12-03 11:07 ` Zdenek Kabelac
2015-12-03 11:27 ` Baolin Wang
2015-12-03 15:49 ` Mikulas Patocka
2015-12-04 4:58 ` Baolin Wang
2015-12-03 15:47 ` Mikulas Patocka
2015-12-04 4:57 ` Baolin Wang
2015-11-12 9:05 ` Christoph Hellwig
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=20151112100422.GM12392@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agk@redhat.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=baolin.wang@linaro.org \
--cc=bart.vanassche@sandisk.com \
--cc=dineshg@quicinc.com \
--cc=dm-devel@redhat.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=snitzer@redhat.com \
--cc=tj@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).