From: Milan Broz <mbroz@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm_crypt: very low performance of random IO operations
Date: Tue, 07 Sep 2010 22:06:35 +0200 [thread overview]
Message-ID: <4C869B4B.706@redhat.com> (raw)
In-Reply-To: <4C80B1B9.6040809@gmail.com>
On 09/03/2010 10:28 AM, Yakov Hrebtov wrote:
> I'm experirncing problems with performance of random IO operations of
> dm_crypt-encrypted devices.
> Sequential IO is good (using AES-NI gives almost no difference comparing with
> unencrypted device), but random IO is poor comparing with unencrypted devices.
Just info for the list - this mail is duplicate of
https://bugzilla.kernel.org/show_bug.cgi?id=17892
so let's use this BZ to track it.
I have some ideas how to improve it, but the change must follow patches which
are currently waiting for upstream inclusion.
(Actually the per-cpu thread patches helps in this case too as side effect.)
Milan
prev parent reply other threads:[~2010-09-07 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 8:28 dm_crypt: very low performance of random IO operations Yakov Hrebtov
2010-09-07 20:06 ` Milan Broz [this message]
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=4C869B4B.706@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-devel@redhat.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.