From: Milan Broz <mbroz@redhat.com>
To: "Günter Merz" <lotan_rm@hotmail.com>,
dm-crypt@saout.de, "Mikulas Patocka" <mpatocka@redhat.com>
Subject: Re: [dm-crypt] md + dm-crypt + lvm2: I/O slows down system, I/O schedule ineffective
Date: Thu, 23 Feb 2012 13:23:59 +0100 [thread overview]
Message-ID: <4F462FDF.4030308@redhat.com> (raw)
In-Reply-To: <20120223115436.GF17572@agk-dp.fab.redhat.com>
On 02/23/2012 12:54 PM, Alasdair G Kergon wrote:
> Check everything is aligned properly.
>
> Maybe test this dm-crypt performance proposal too:
> http://people.redhat.com/mpatocka/patches/kernel/dm-crypt-paralelizace/current/series.html
Just note, this is not yet stable repository and final patches
will change (or perhaps some patches will not be committed,
depends on testing output).
IOW - if you can experiment with your data, try it, otherwise please wait
until it is in upstream repo.
Thanks,
Milan
prev parent reply other threads:[~2012-02-23 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 10:19 [dm-crypt] md + dm-crypt + lvm2: I/O slows down system, I/O schedule ineffective Günter Merz
2012-02-23 10:57 ` Marc Ballarin
2012-02-23 11:54 ` Alasdair G Kergon
2012-02-23 12:23 ` 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=4F462FDF.4030308@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=lotan_rm@hotmail.com \
--cc=mpatocka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox