All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: dave b <db.pub.mail@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] [BUG] bad performance and system stalls when using dm-crypt
Date: Sun, 12 Sep 2010 11:07:00 +0200	[thread overview]
Message-ID: <4C8C9834.8060201@redhat.com> (raw)
In-Reply-To: <AANLkTikLSFFpbgX+rBR5banBygmB6rRvzMBYKfPcFPuJ@mail.gmail.com>

On 09/12/2010 10:36 AM, dave b wrote:
> 
> Should I forward my 'bug' to the linux kernel maliing list ?

Better report it to kernel bugzilla, it is better for tracking.
(Also see https://bugzilla.kernel.org/show_bug.cgi?id=17892 )

Anyway, there are some patches waiting for inclusion in DM tree
for weeks and all fixes must follow these changes. Also replacing
io barriers in 2.6.37 can interfere here (fsync uses barriers).

Anyway, if you have some tests which you found useful for dm-crypt
testing, attach them to bugzilla too. I would like them to run
for all kernels in the future to avoid performance regressions.

Milan

  parent reply	other threads:[~2010-09-12  9:07 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
2010-09-12  9:07           ` Milan Broz [this message]
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=4C8C9834.8060201@redhat.com \
    --to=mbroz@redhat.com \
    --cc=db.pub.mail@gmail.com \
    --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.