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 tFEwk2ahY9PK for ; Sun, 17 Mar 2013 23:55:21 +0100 (CET) Received: from awesome.dsw2k3.info (awesome.dsw2k3.info [IPv6:2a01:198:661:1f::3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sun, 17 Mar 2013 23:55:21 +0100 (CET) Date: Sun, 17 Mar 2013 23:55:16 +0100 From: Matthias Schniedermeyer Message-ID: <20130317225516.GA6053@citd.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: Subject: Re: [dm-crypt] unusual writing speeds when benchmark speeds are high enough List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ".. ink .." Cc: dm-crypt@saout.de On 17.03.2013 17:36, .. ink .. wrote: > Sorry for my previous email without a title,resending the email with a > title this time. >=20 > A user of cryptsetup(through zuluCrypt) asked me a question i can not > answer and asking it here. >=20 > In his system,"cryptsetup benchmark" gives the following results: >=20 > [root sheep 13] ~ > cryptsetup benchmark > # Tests are approximate using memory only (no storage IO). > PBKDF2-sha1 341333 iterations per second > PBKDF2-sha256 193607 iterations per second > PBKDF2-sha512 64125 iterations per second > PBKDF2-ripemd160 303758 iterations per second > PBKDF2-whirlpool 64125 iterations per second > # Algorithm | Key | Encryption | Decryption > aes-cbc 128b 183,6 MiB/s 215,4 MiB/s > serpent-cbc 128b 68,0 MiB/s 68,9 MiB/s > twofish-cbc 128b 167,7 MiB/s 177,5 MiB/s > aes-cbc 256b 142,3 MiB/s 161,5 MiB/s > serpent-cbc 256b 69,7 MiB/s 67,0 MiB/s > twofish-cbc 256b 170,1 MiB/s 177,8 MiB/s > aes-xts 256b 201,2 MiB/s 205,6 MiB/s > serpent-xts 256b 69,7 MiB/s 67,6 MiB/s > twofish-xts 256b 180,5 MiB/s 175,6 MiB/s > aes-xts 512b 147,0 MiB/s 152,5 MiB/s > serpent-xts 512b 70,5 MiB/s 67,8 MiB/s > twofish-xts 512b 182,0 MiB/s 176,0 MiB/s >=20 > The system is decent enought. >=20 > The write speed he is getting though through the mapper is unusually > slow,the test is below: >=20 >=20 > [root sheep 8] ~ > dd if=3D/dev/zero of=3Dtest.img bs=3D70M count=3D1 > 1+0 Datens=E4tze ein > 1+0 Datens=E4tze aus > 73400320 Bytes (73 MB) kopiert, 2,58497 s, 28,4 MB/s >=20 > [17.03.2013 21:50 Uhr] > [root sheep 9] ~ > cryptsetup create test test.img > Passsatz eingeben: >=20 > [17.03.2013 21:51 Uhr] > [root sheep 10] ~ > dd if=3D/dev/zero of=3D/dev/mapper/test bs=3D10M= count=3D1 > 1+0 Datens=E4tze ein > 1+0 Datens=E4tze aus > 10485760 Bytes (10 MB) kopiert, 67,2014 s, 156 kB/s >=20 > [17.03.2013 21:52 Uhr] > [root sheep 11] ~ > cryptsetup remove test >=20 > As the test show,He is getting 156kB/s when using dd over the encryption > mapper verses 28MB/s when using dd straight. dd was with conv=3Dfsync? Otherwise you are measuring buffer cache. > Where is the wrong in his system? version of cryptsetup used is 1.6.0 I would say, there are quite a few details missing. Hardware, Software? 28.4 MB/s also isn't what i would call fast, what is that? --=20 Matthias