mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yan Li <elliot.li.tech@gmail.com>
To: Milan Broz <mbroz@redhat.com>
Cc: Yan Li <elliot.li.tech@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ritesh Raj Sarraf <rrs@researchut.com>,
	Christophe Saout <christophe@saout.de>,
	linux-kernel@vger.kernel.org, dm-devel@redhat.com,
	Herbert Xu <herbert@gondor.apana.org.au>,
	rjmaomao@gmail.com, Alasdair G Kergon <agk@redhat.com>,
	dm-crypt@saout.de
Subject: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
Date: Mon, 2 Jun 2008 20:31:45 +0800	[thread overview]
Message-ID: <20080602123145.GA8258@yantp.cn.ibm.com> (raw)
In-Reply-To: <48439890.6030904@redhat.com>

Hi Milan,

On Mon, Jun 02, 2008 at 08:52:00AM +0200, Milan Broz wrote:
> Please could you try if  patch here helps and doesn't cause performance degradation?
> http://www2.kernel.org/pub/linux/kernel/people/agk/patches/2.6/2.6.25/dm-crypt-add-cond_resched.patch

Will the result of testing a Debian 2.6.24-etchnhalf.1-amd64 kernel
(very near a vanilla kernel) be of same value?  Since the data on some
other drives on this server is important so I dare not try 2.6.25-rc
on it.

Following is my test plan, comments are welcomed:

Test command:
# dd if=/dev/zero of=/dev/mapper/open_device bs=500M count=10
(this server has 2G memory)

The command will be run	for 3 times, and average speed of last two
runs will be taken as result score.

Dm-crypt LUKS Encryption scenarios:
aes-cbc-essiv:sha256, keysize 128
aes-xts-plain, keysize 256
aes-xts-plain, keysize 512

I will compare the speed of all above 3 encryption scenarios, with and
without the patch.

--
Li, Yan

  reply	other threads:[~2008-06-02 12:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 13:54 Ritesh Raj Sarraf
2008-02-29  7:20 ` Andrew Morton
2008-02-29 18:15   ` Herbert Xu
2008-02-29 18:46   ` [dm-devel] " Alasdair G Kergon
2008-02-29 18:59     ` Ritesh Raj Sarraf
2008-03-01 19:30       ` Milan Broz
2008-03-01 19:33         ` Milan Broz
2008-03-01 21:59           ` Gunter Ohrner
2008-03-02  7:58             ` Gunter Ohrner
2008-03-06 14:41           ` [dm-devel] " Ritesh Raj Sarraf
2008-06-02  3:07   ` Yan Li
2008-06-02  6:52     ` Milan Broz
2008-06-02 12:31       ` Yan Li [this message]
2008-06-02 12:51         ` Milan Broz
2008-06-05 22:44           ` Yan Li
2008-06-06  6:46             ` Milan Broz
     [not found]         ` <2f83bcba0806031246m30f92892wc868d81a9c29d680@mail.gmail.com>
2008-06-03 23:13           ` Yan Li

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=20080602123145.GA8258@yantp.cn.ibm.com \
    --to=elliot.li.tech@gmail.com \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=christophe@saout.de \
    --cc=dm-crypt@saout.de \
    --cc=dm-devel@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@redhat.com \
    --cc=rjmaomao@gmail.com \
    --cc=rrs@researchut.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

all inboxes | Powered by JetHome®