All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] [BUG] bad performance and system stalls when using dm-crypt
Date: Sun, 12 Sep 2010 11:04:20 +0200	[thread overview]
Message-ID: <20100912090420.GA4674@fancy-poultry.org> (raw)
In-Reply-To: <AANLkTikLSFFpbgX+rBR5banBygmB6rRvzMBYKfPcFPuJ@mail.gmail.com>

On 12.09.2010, dave b wrote: 

> Should I forward my 'bug' to the linux kernel maliing list ?

I'm not shure at all what causes the behaviour you encounter, there is 
the device-mapper, the crypto layer, the disk scheduler and a lot more
which could be more or less related. 

There was a similar monster thread some months ago on latency issues
(which was not crypto related!), Linus did a "yum update" in the
background while reading mail with Alpine and encountered some severe
stalls. A lot of work has been put into cfq afterwards, and latency is a
still ongoing issue in the Linux kernel and on the lkml (see the patch
from M. Desnoyers which came up today regarding sched granularity).

In a nutshell: I don't know :-)

  reply	other threads:[~2010-09-12  9:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-11  6:06 [dm-crypt] [BUG] bad performance and system stalls when using dm-crypt dave b
2010-09-11  6:57 ` Heinz Diehl
2010-09-11  8:11   ` dave b
2010-09-11  9:02     ` dave b
2010-09-11  9:08       ` dave b
2010-09-12  8:36         ` dave b
2010-09-12  9:04           ` Heinz Diehl [this message]
2010-09-12  9:07           ` Milan Broz
2010-09-12 10:42             ` dave b
2010-09-12 10:45             ` dave b
2010-10-06 17:58               ` dave b
2010-10-24 15:32                 ` Fwd: " dave b
2010-10-24 16:31                   ` Milan Broz
2010-10-24 16:52                     ` dave b
2010-10-24 17:05                       ` Milan Broz

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=20100912090420.GA4674@fancy-poultry.org \
    --to=htd@fancy-poultry.org \
    --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 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.