From: Milan Broz <mbroz@redhat.com>
To: Marc MERLIN <marc@merlins.org>
Cc: dm-crypt@saout.de, Yves-Alexis Perez <corsac@debian.org>
Subject: Re: [dm-crypt] aes-xts-plain with aes_x86_64 makes my SSD 5x slower than my encrypted HD
Date: Tue, 24 Jul 2012 15:54:06 +0200 [thread overview]
Message-ID: <500EA8FE.3010303@redhat.com> (raw)
In-Reply-To: <20120724055722.GA15507@merlins.org>
On 07/24/2012 07:57 AM, Marc MERLIN wrote:
> Mmmh, so I installed "standard" linux-image-3.2.0-3-amd64 from debian.
> And....
> nothing changed :(
Well. I found SSD where I can reproduce something similar.
Seems page cache messes something with readahead...
# lsblk /dev/sdc -t
NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE
sdc 0 512 0 512 512 0 noop 128
└─sdc_null_crypt (dm-0) 0 512 0 512 512 0 128
- Disable readahead
# blockdev --setra 0 /dev/mapper/sdc_null_crypt
# hdparm -t /dev/mapper/sdc_null_crypt
Timing buffered disk reads: 106 MB in 3.01 seconds = 35.18 MB/sec
(pretty bad)
But with direct-io it still works:
# hdparm --direct -t /dev/mapper/sdc_null_crypt
Timing O_DIRECT disk reads: 698 MB in 3.00 seconds = 232.44 MB/sec
(now with read-ahead set to 4M)
# blockdev --setra 8192 /dev/mapper/sdc_null_crypt
# hdparm -t /dev/mapper/sdc_null_crypt
Timing buffered disk reads: 664 MB in 3.00 seconds = 221.29 MB/sec
So. Can you please try to increase readahead (and also run it with direct-io)?
Just to check if it is the same problem or not...
Thanks,
Milan
next prev parent reply other threads:[~2012-07-24 13:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 19:07 [dm-crypt] aes-xts-plain with aes_x86_64 makes my SSD 5x slower than my encrypted HD Marc MERLIN
2012-07-22 19:47 ` Yves-Alexis Perez
2012-07-22 20:39 ` Marc MERLIN
2012-07-22 21:47 ` Arno Wagner
2012-07-23 6:07 ` Yves-Alexis Perez
2012-07-23 6:28 ` Marc MERLIN
2012-07-23 8:14 ` Arno Wagner
2012-07-23 10:46 ` Milan Broz
2012-07-23 11:09 ` Yves-Alexis Perez
2012-07-23 11:37 ` Milan Broz
2012-07-23 15:08 ` André Gall
2012-07-23 17:27 ` André Gall
2012-07-24 14:06 ` Heinz Diehl
2012-07-24 14:16 ` Milan Broz
2012-07-23 16:12 ` Marc MERLIN
2012-07-23 16:19 ` Yves-Alexis Perez
2012-07-23 17:54 ` Marc MERLIN
2012-07-23 19:26 ` Yves-Alexis Perez
2012-07-23 17:15 ` Milan Broz
2012-07-23 17:51 ` Marc MERLIN
2012-07-23 21:31 ` Milan Broz
2012-07-24 5:57 ` Marc MERLIN
2012-07-24 6:25 ` Heinz Diehl
2012-07-24 15:02 ` Marc MERLIN
2012-07-24 15:19 ` Milan Broz
2012-07-24 16:09 ` Marc MERLIN
2012-07-24 13:54 ` Milan Broz [this message]
[not found] ` <500E9099.8050501@redhat.com>
2012-07-24 14:27 ` Heinz Diehl
2012-07-24 14:58 ` Heinz Diehl
2012-07-24 15:38 ` Marc MERLIN
2012-07-24 16:48 ` Heinz Diehl
2012-07-24 6:11 ` Heinz Diehl
2012-07-22 21:55 ` Marc MERLIN
2012-07-22 20:22 ` Heinz Diehl
2012-08-12 12:49 ` Pasi Kärkkäinen
2012-08-16 7:43 ` Marc MERLIN
[not found] ` <502D1F96.3080905@andregall.de>
2012-08-16 17:57 ` Marc MERLIN
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=500EA8FE.3010303@redhat.com \
--to=mbroz@redhat.com \
--cc=corsac@debian.org \
--cc=dm-crypt@saout.de \
--cc=marc@merlins.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox