[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Nov 2015 17:31:43 +0800
From: Baolin Wang <baolin.wang@...aro.org>
To: axboe@...nel.dk, agk@...hat.com, snitzer@...hat.com,
dm-devel@...hat.com, neilb@...e.com
Cc: jack@...e.cz, tj@...nel.org, jmoyer@...hat.com,
keith.busch@...el.com, bart.vanassche@...disk.com,
linux-raid@...r.kernel.org, broonie@...nel.org, arnd@...db.de,
dineshg@...cinc.com, linux-kernel@...r.kernel.org,
baolin.wang@...aro.org
Subject: [PATCH 0/2] Introduce the request handling for dm-crypt
Now the dm-crypt code only implemented the 'based-bio' method to encrypt/
decrypt block data, which can only hanle one bio at one time. As we know,
one bio must use the sequential physical address and it also has a limitation
of length. Thus it may limit the big block encyrtion/decryption when some
hardware support the big block data encryption.
This patch series introduc the 'based-request' method to handle the data
encryption/decryption. One request can contain multiple bios, so it can
handle big block data to improve the efficiency.
Also this patch refers to the Dinesh K Garg <dineshg@...eaurora.org> and
franciscofranco <franciscofranco.1990@...il.com> submission of 'Request
based dm-crypt', and the original link is:
https://github.com/major91/Zeta-Chromium-N5/commit/621d4821da04cfde383329ebdf4ce8711ec3329c
Now it can encrypt/decrypt successfully with read/write testing, and it shows
some efficiency improvements with hardware acceleration. But I really hope to
need more comments about the structure and conception. Thanks for your review.
Baolin Wang (2):
block: Introduce BIO_ENDIO_FREE for bio flags
md: dm-crypt: Introduce the request handling for dm-crypt
block/blk-core.c | 6 +-
drivers/md/Kconfig | 6 +
drivers/md/dm-crypt.c | 831 ++++++++++++++++++++++++++++++++++++++++-
drivers/md/dm.c | 13 +-
include/linux/blk_types.h | 6 +
include/linux/device-mapper.h | 5 +
6 files changed, 861 insertions(+), 6 deletions(-)
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists