From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lozEGTl9rqIw for ; Sat, 24 Nov 2012 21:59:19 +0100 (CET) Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 24 Nov 2012 21:59:18 +0100 (CET) Received: by mail-ee0-f50.google.com with SMTP id b45so5474924eek.37 for ; Sat, 24 Nov 2012 12:59:18 -0800 (PST) Message-ID: <50B13522.1000003@gmail.com> Date: Sat, 24 Nov 2012 21:59:14 +0100 From: Milan Broz MIME-Version: 1.0 References: <50AEF7B3.4000807@babioch.de> <20121123060720.GA5520@tansi.org> <2fffc2e10dfbf0a7ccaaf2ef43213a4e.squirrel@ssl.verfeiert.org> In-Reply-To: <2fffc2e10dfbf0a7ccaaf2ef43213a4e.squirrel@ssl.verfeiert.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Reconsidering default options for cryptsetup-reencrypt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 11/24/2012 06:01 PM, Sven Eschenberg wrote: > BTW, what exactly are you referring to, when you talk about 64 MB blocksize? Here cryptsetup-reencrypt is in principle simple program, it reads a "block" and write it back to device with new encryption parameters (and optionally with some different offset). So block here is meant as an unit which is handled in one reencryption step. (But the real atomic unit of encryption is still 512B block of course.) There is no requirement this block to be aligned to underlying hw alignment (but if it is misaligned, the same performance degradation problems apply of course). Milan