From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] HDD sector size interrelated with dm-crypt?
Date: Thu, 17 Mar 2011 16:08:36 +0100 [thread overview]
Message-ID: <4D8223F4.3020005@redhat.com> (raw)
In-Reply-To: <20110317152918.e7bfac44.taeuber@bbaw.de>
On 03/17/2011 03:29 PM, Lars Täuber wrote:
> 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?
dmcrypt always uses 512 bytes sector for encryption, it cannot be changed
easily to 4k sectors (internal block layer bio structure and device-mapper
always counts in 512 sectors).
I do not think that with accelerated encryption like AES-NI the speed up
would be so visible.
But the whole stack (including device-mapper) properly aligns
to drive sector size, so it will work with 4k drives without problems.
I think many people is already using it on true 4k drives.
In fact mapping sector is the block layer problem, device-mapper targets
just propagates block size information up the stack.
Milan
prev parent reply other threads:[~2011-03-17 15:08 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
2011-03-17 15:04 ` Christoph Anton Mitterer
2011-03-17 15:08 ` Milan Broz [this message]
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=4D8223F4.3020005@redhat.com \
--to=mbroz@redhat.com \
--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.