From: Hanno Foest <hurga-crypt@tigress.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Slow I/O with LUKS on amd64
Date: Tue, 15 Mar 2011 01:44:09 +0100 [thread overview]
Message-ID: <20110315004409.GF7787@tigress.com> (raw)
On Wed Mar 9 09:11:21 CET 2011, Thomas Damgaard wrote:
> I have recently switched from i386 to amd64. After switching to 64
> bit, I/O on LUKS encrypted devices became horribly slow.
I had the same issue with Ubuntu 10.10. After installing a kernel from
the upcoming 11.04, doing a 'time /usr | wc -l' went from 3 minutes to 6
seconds. And yes, I dropped my caches. :)
I installed the following image, BTW:
//launchpadlibrarian.net/65900455/linux-image-2.6.38-6-generic_2.6.38-6.34_amd64.deb
Hanno
next reply other threads:[~2011-03-15 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 0:44 Hanno Foest [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-09 8:11 [dm-crypt] Slow I/O with LUKS on amd64 Thomas Damgaard
2011-03-09 10:21 ` Milan Broz
2011-03-09 14:38 ` Carlo Wood
2011-03-09 15:46 ` Milan Broz
[not found] ` <AANLkTinTsUxYz1_ANqnsqjVejAM39oi7eC=2nqwiyjcn@mail.gmail.com>
[not found] ` <4D77BB5B.8090007@redhat.com>
2011-03-10 13:36 ` Thomas Damgaard
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=20110315004409.GF7787@tigress.com \
--to=hurga-crypt@tigress.com \
--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