From: Andi Kleen <ak@muc.de>
To: Christophe Saout <christophe@saout.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2][RFC] Add dm-crypt target
Date: Mon, 22 Dec 2003 23:29:56 +0100 [thread overview]
Message-ID: <m3d6aga3kr.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <15Gg9-4H6-25@gated-at.bofh.it> (Christophe Saout's message of "Mon, 22 Dec 2003 23:00:25 +0100")
Christophe Saout <christophe@saout.de> writes:
> this is the actual dm-crypt target. It uses cryptoapi to achive the same
> goal as cryptoloop.
>
> It uses mempools to ensure not to ever run out of memory and can split
> large IOs into smaller ones under memory pressure.
>
> Tested by some people, also works on a swap device.
Is the IV argument compatible to block backed loop?
If not it would not be possible to use existing block based
loop crypto file systems this way.
-Andi
next parent reply other threads:[~2003-12-23 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15G6g-4oz-17@gated-at.bofh.it>
[not found] ` <15Gg9-4H6-25@gated-at.bofh.it>
2003-12-22 22:29 ` Andi Kleen [this message]
2003-12-23 15:11 ` [PATCH 2/2][RFC] Add dm-crypt target Christophe Saout
2003-12-22 21:42 loop driver, device-mapper and crypto Christophe Saout
2003-12-22 21:52 ` [PATCH 2/2][RFC] Add dm-crypt target Christophe Saout
2003-12-22 23:07 ` Jeff Garzik
2003-12-22 23:24 ` Mike Fedyk
2003-12-22 23:29 ` Jeff Garzik
2003-12-22 23:50 ` Mike Fedyk
2003-12-23 0:10 ` Christophe Saout
2003-12-23 2:53 ` Rusty Russell
2003-12-23 13:13 ` Christoph Hellwig
2003-12-23 13:36 ` Christophe Saout
2003-12-23 15:15 ` Joe Thornber
2003-12-23 15:31 ` Jeff Garzik
2003-12-23 15:43 ` Joe Thornber
2003-12-23 17:01 ` Christophe Saout
2003-12-23 17:15 ` Joe Thornber
2003-12-23 17:14 ` Jeff Garzik
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=m3d6aga3kr.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=christophe@saout.de \
--cc=linux-kernel@vger.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 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.