All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Ballarin <Ballarin.Marc@gmx.de>
To: "Günter Merz" <lotan_rm@hotmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] md + dm-crypt + lvm2: I/O slows down system, I/O schedule ineffective
Date: Thu, 23 Feb 2012 11:57:27 +0100	[thread overview]
Message-ID: <4F461B97.7020000@gmx.de> (raw)
In-Reply-To: <BAY171-W21218AF052228CC456EBB7F7650@phx.gbl>

Hi,

Am 23.02.2012 11:19, schrieb Günter Merz:
> I'm experiencing unresponsiveness and a general system slowdown when I'm unpacking big archives or building a big packages (during builds I'm only using max 2 cores). To counter this, I've been experimenting with nice and ionice. Unfortunately, ionice -c3 before big I/O traffic doesn't seem to make any difference. The responsiveness is still really bad at times.
This sounds like those (more or less) well-known hugepage issues.

You could try "echo madvise > 
/sys/kernel/mm/transparent_hugepage/defrag" (or "echo never...") if your 
kernel is configured to use transparent hugepages (which most modern 
distribution kernels are).

If this is your issue, the bug isn't really caused by dm-crypt, but by 
Linux memory management issues and it is completely unrelated to ionice 
or io scheduler settings.

Regards,
Marc

  reply	other threads:[~2012-02-23 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 10:19 [dm-crypt] md + dm-crypt + lvm2: I/O slows down system, I/O schedule ineffective Günter Merz
2012-02-23 10:57 ` Marc Ballarin [this message]
2012-02-23 11:54 ` Alasdair G Kergon
2012-02-23 12:23   ` 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=4F461B97.7020000@gmx.de \
    --to=ballarin.marc@gmx.de \
    --cc=dm-crypt@saout.de \
    --cc=lotan_rm@hotmail.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 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.