All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Cc: ".. ink .." <mhogomchungu@gmail.com>
Subject: Re: [dm-crypt] unusual writing speeds when benchmark speeds are high enough
Date: Mon, 18 Mar 2013 07:22:01 +0100	[thread overview]
Message-ID: <5146B289.5020807@gmail.com> (raw)
In-Reply-To: <CAFnMBaRk7m60fdYvcKMHET7H0bocYCq2k0VukgbO+hF=bv6E-A@mail.gmail.com>

Please note that "benchmark" test is just appoximate.

If there is a problem with IO (storage - alignment etc)
always try to test with empty cipher - just use
-c null in luksFormat
(NOTE: this is plain copy, NO ENCRYPTION)
Available since http://code.google.com/p/cryptsetup/wiki/Cryptsetup143

This way you can check if the problem is in dmcrypt
overhead or some storage misconfiguration (data alignment etc).
(-c null will cause no kernel crypto is used at all, it is
plain data copy, just using the same dmcrypt IO path).

Also try direct io (add oflag=direct to dd) etc.
(This will eliminate page cache effect.)

In any case, try underlying device directly, then add another
layer, one per every step (LUKS, LVM, RAID, ...) so you can see where
is the problem. (See lsblk how the storage stack looks like.)

Milan

On 18.3.2013 0:19, .. ink .. wrote:
> I have asked the person for answers to the following questions,did i miss any useful question? I will report the answers when i get them
>
> what are your computer specifications?
>
> what kernel version are you running?
>
> are you on a 64 bit or 32 bit system?
>
> did you try the test on your hard drive with the OS or on a USB stick?
>
> did you run the test on an LVM volume or RAID device?
>
> A few more tests would be useful too,what do these commands give you?
>
> dd if=/dev/zero of=test1.img bs=10M count=1
>
> dd if=/dev/urandom of=test2.img bs=10M count=1
>
>
>
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>

  reply	other threads:[~2013-03-18  6:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 21:36 [dm-crypt] unusual writing speeds when benchmark speeds are high enough .. ink ..
2013-03-17 22:55 ` Matthias Schniedermeyer
2013-03-18  6:42   ` .. ink ..
2013-03-18  8:37     ` Matthias Schniedermeyer
2013-03-18 10:01       ` Heinz Diehl
2013-03-18 10:20         ` Arno Wagner
2013-03-18 10:43         ` Matthias Schniedermeyer
2013-03-17 23:07 ` Arno Wagner
2013-03-17 23:19   ` .. ink ..
2013-03-18  6:22     ` Milan Broz [this message]
2013-03-18  7:58       ` .. ink ..
2013-03-18 18:16   ` .. ink ..
2013-03-18  7:06 ` Heinz Diehl

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=5146B289.5020807@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=mhogomchungu@gmail.com \
    /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.