From: Marc MERLIN <marc@merlins.org>
To: "Yves-Alexis Perez" <corsac@debian.org>,
"André Gall" <dm-crypt@andregall.de>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] aes-xts-plain with aes_x86_64 makes my SSD 5x slower than my encrypted HD
Date: Mon, 23 Jul 2012 10:54:23 -0700 [thread overview]
Message-ID: <20120723175423.GB15867@merlins.org> (raw)
In-Reply-To: <500D8993.7030802@andregall.de> <1343060350.26887.20.camel@scapa>
On Mon, Jul 23, 2012 at 06:19:10PM +0200, Yves-Alexis Perez wrote:
> > I'll try rebuilding a non preempt kernel just in case.
>
> Maybe try with Debian kernel first? It's just an apt-get install away
> and will give you a setup identical as mine.
I have a custom initramfs, it was easier to compile a new kernel than to try
and get the debian one to boot my system :)
But for reference, what kernel package are you using?
On Mon, Jul 23, 2012 at 07:27:47PM +0200, André Gall wrote:
> I remember a test which I conducted after I received my Intel SDD 510
> 120 GB about 1 year ago. I don't remember all the details, but the
> essence was that write speed decreased dramatically if the write process
> wasn't aligned.
> I did:
> dd if=/dev/zero of=/dev/sda bs=4k
> I got around 400 Mb/sec, which was expected. But when I did:
>
> dd if=/dev/zero of=/dev/sda bs=5k
> I got only around 40 Mb/sec
Yes, write alignment and write amplification are definitely issues on SSDs,
but note how I was only doing read tests :)
See
http://www.void.gr/kargig/blog/2012/01/11/linux-ssd-partition-alignment-tips/
Cheers,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2012-07-23 17: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 [this message]
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
[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=20120723175423.GB15867@merlins.org \
--to=marc@merlins.org \
--cc=corsac@debian.org \
--cc=dm-crypt@andregall.de \
--cc=dm-crypt@saout.de \
/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