public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>
To: linux-kernel@vger.kernel.org
Cc: dm-devel@redhat.com, dm-crypt@saout.de
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in	dm-crypt
Date: Sat, 01 Mar 2008 22:59:33 +0100	[thread overview]
Message-ID: <fqcjj9$5bv$1@ger.gmane.org> (raw)
In-Reply-To: 47C9AF8F.2050502@redhat.com

Milan Broz wrote:
> (the same patch for 2.6.24)

Observations using this patch:

* I did not get a Soft Lockup during my tests so far.

* The latency problems I experienced when writing massive amounts of data to
  an encrypted partitions are improved, though not solved. Using the "dd
  if=/dev/zero of=test.null bs=4M count=1024 ; rm test.null" approach
  mentioned in the other thread, the system stays more responsive and even
  listening to music works more or less, although there are still audible
  interruptions. A few times during the write, CPU usage will spike and IO
  (including music playing in Amarok) will stall for about 0.5 seconds or a
  second.

* This patch seems to hurt performance, I got much lower thoughput and the
  system was never fully loaded, ie. gkrellm showed both cores to run
  between 10% and 40% with a combined CPU utilization fo 30% most of the
  time.
  I got unstable timings from my dd command, but targetting the reiserfs
  partition I got around 18 MB/sec and 34 MB/sec instead of the 41 MB/sec I
  achieved in my tests yesterday.
  So this looks like a viable work around if it reliably avoids the Soft
  Lockup, but it does not seem to be a perfect solution.
  (Addendum: I just got 41 MB/sec with this patch, with an otherwise nearly
  idle system, ie. lots of active processes but none doing anything serious.
  The numbers before applying the patch were much more stable and generally
  higher. Now simply playing or not playing an OGG seems to make the
  difference between 40 MB/sec and 30 MB/sec.)

Greetings,

  Gunter


  reply	other threads:[~2008-03-01 22:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 13:54 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt 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 [this message]
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
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='fqcjj9$5bv$1@ger.gmane.org' \
    --to=g.ohrner@post.rwth-aachen.de \
    --cc=dm-crypt@saout.de \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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