All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: martin f krafft <madduck@madduck.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Abysmal I/O scheduling with dm-crypt
Date: Mon, 19 Sep 2011 14:39:09 -0400	[thread overview]
Message-ID: <10932.1316457549@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 30 Aug 2011 09:14:07 +0200." <20110830071407.GA8165@albatross.gern.madduck.net>

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

On Tue, 30 Aug 2011 09:14:07 +0200, martin f krafft said:
> I am using encrypted filesystems (dm-crypt) and the 3.0.0 kernel.
> Underneath might be a RAID1 or a fast SSD. On top is usually LVM
> with a few LVs holding the system.
> 
> Whenever an I/O-intensive task starts, such as:

> the system becomes unusable for several seconds at a time, at least
> once or twice per minute.

Sorry for the late reply - I've seen similar on my laptop.  However, I haven't
dug further into it, because the use case that causes the most pain is backing
up the laptop to a LUKS partition on an external USB drive - and I usually
start that and go to bed so it's not-a-problem.   Also, it only wedges up
those processes that actually try to do disk I/O - which means that all
the terminal windows that are running SSH to various servers don't
usually take a hit and things don't get "unusable" in the sense of "totally
weged and locked up".

But I can at least confirm you're not hallucinating. :)



[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2011-09-19 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  7:14 Abysmal I/O scheduling with dm-crypt martin f krafft
2011-09-05 15:37 ` Jan Kara
2011-09-08  2:51   ` Dan Merillat
2011-09-19 18:39 ` Valdis.Kletnieks [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=10932.1316457549@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madduck@madduck.net \
    /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.