From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 16 Nov 2010 13:00:16 +0100 (CET) Message-ID: <4CE27248.5010205@redhat.com> Date: Tue, 16 Nov 2010 13:00:08 +0100 From: Milan Broz MIME-Version: 1.0 References: <566573504.20101115153604@novg.net> <4CE142C3.1070408@redhat.com> <737699007.20101116103102@novg.net> <4CE24E02.8030608@redhat.com> <1373448030.20101116143225@novg.net> In-Reply-To: <1373448030.20101116143225@novg.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] AES-XTS performance List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Novgorodov Cc: dm-crypt@saout.de On 11/16/2010 12:32 PM, Igor Novgorodov wrote: > Such big difference between read and write speed is by design? > Or it is a problem of my setup? Maybe i should try to disable > hyperthreading and check again? That should be probably improved later. (btw I just fixed stacking there, it was written by Andi Kleen). Anyway, now I need to check that there is no known data corruption with this approach and then we can add another patches on top of it. (Targeted for 2.6.38, it missed 2.6.37 merge window already.) (If anyone see some reproducible data corruption when using this patch, please let me know.) Milan