From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Encrypting with larger packet size
Date: Tue, 22 Jan 2013 06:42:23 +0100 [thread overview]
Message-ID: <20130122054223.GA25850@tansi.org> (raw)
In-Reply-To: <CAO6to9U73_XPXA2oraF2rb8ktwVnnTwR4esJyW6bXYVO_xPxAg@mail.gmail.com>
Why would you want to do this? There doe snot seem to be any
good reason...
Arno
On Mon, Jan 21, 2013 at 08:18:50PM -0800, Dinesh Garg wrote:
> Hi,
>
> Currently dm-crypt encrypts the block device using sector size. Is it
> possible to change this to use larger sizes such as 8K or 16K or larger? If
> not possible currently, what would it take to make that possible i..e what
> are the problems that we need to fix?
>
> Is it DM layer that restricts us to use larger sizes or file system due to
> its block size?
>
> I have one more question: How does a read operation ends up at calling
> dm-crypt api?
>
> Thanks,
> DG
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2013-01-22 5:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 4:18 [dm-crypt] Encrypting with larger packet size Dinesh Garg
2013-01-22 5:42 ` Arno Wagner [this message]
2013-01-22 6:04 ` Dinesh Garg
2013-01-22 7:24 ` Milan Broz
2013-01-22 8:00 ` Dinesh Garg
2013-01-22 15:54 ` Milan Broz
2013-01-24 19:44 ` Dinesh Garg
2013-01-25 23:25 ` Arno Wagner
2013-01-28 12:00 ` [dm-crypt] Encrypting with larger packet size (+some experimental patch) Milan Broz
2013-03-05 11:53 ` Michael Stapelberg
2013-03-10 15:05 ` Milan Broz
2013-03-25 19:22 ` Michael Stapelberg
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=20130122054223.GA25850@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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.