From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] HDD sector size interrelated with dm-crypt?
Date: Thu, 17 Mar 2011 16:03:04 +0100 [thread overview]
Message-ID: <20110317150303.GA4997@tansi.org> (raw)
In-Reply-To: <20110317152918.e7bfac44.taeuber@bbaw.de>
Should not matter. Also a speed increase is unlikely,
disks are still dog-slow compared to things the CPU does, like
encrypting sectors. They are not written/read individually
anyways in most cases.
Arno
On Thu, Mar 17, 2011 at 03:29:18PM +0100, Lars T??uber wrote:
> Hi there,
>
> does dm-crypt depend in any way on the sector size of the block device to be encrypted?
> So the real question is: Does dm-crypt work as expected on a 4KiB sector sized SATA drive when there is no translation to 512B sector size? Are there options that must be taken then?
>
> I've read somewhere that the encryption algorithm work with 512B block sizes.
> Could this be changed to 4KiB block sizes to gain speed with the upcoming devices?
>
> Thanks
> Lars
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2011-03-17 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:29 [dm-crypt] HDD sector size interrelated with dm-crypt? Lars Täuber
2011-03-17 15:03 ` Arno Wagner [this message]
2011-03-17 15:04 ` Christoph Anton Mitterer
2011-03-17 15:08 ` Milan Broz
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=20110317150303.GA4997@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.