linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Sven-Haegar Koch <haegar@sdinet.de>,
	Dan Merillat <dan.merillat@gmail.com>,
	preining@logic.at, riel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.31 - very swap-happy with plenty of free RAM
Date: Thu, 19 Nov 2009 07:43:02 +0100	[thread overview]
Message-ID: <4B04E8F6.3000004@wpkg.org> (raw)
In-Reply-To: <20091119013810.GO9467@discord.disaster>

Dave Chinner wrote:

>>>> I have a pretty powerful desktop machine with 8 GB RAM, fast disks with
>>>> RAID-1 etc.
>>>> Every 10 minutes or so, machine is really unresponsive, load jumps to 10 or
>>>> 20. Mouse pointer jumps, it's impossible to change between windows etc.
>>> This is the type of hefty workstation many of the core developers
>>> have, running similar workloads, so I'm somewhat surprised that the
>>> default VM settings have this kind of issue.
>>>
>>>> Do a "swapoff -a", and everything is snappy and responsive as it should,
>>>> there are no more lags.
>>> Yes, that's my exact finding.
>>>
>>> Is this weird IO storm happening for anyone else with plenty of memory
>>> (for their taskload?)
>> For me it happend on my laptop. 3gb RAM, and a 1gb VMWare Windows-XP 
>> instance running, plus the usual like firefox, thunderbird, kde4.
>>
>> Without running vmware it did not happen. And since I have now disabled 
>> barriers on the xfs /home partition (on luks crypto lvm) it also does 
>> not happen anymore.
> 
> Yeah, it looks like dm-crypt recently started supporting barriers in
> commit 647c7db14ef9cacc4ccb3683e206b61f0de6dc2b. Hence XFS will have
> detected barriers work at mount time mount and so is now issuing
> them.
> 
> Similarly, raid1 (mirror) has recently gained barrier support so
> the same issue can be seen there.

What is also interesting, that a normal software RAID-1 sync (i.e. from 
a degraded state) does not seem to make any visible effect on system 
responsiveness.

Uncompress a big tar file, or VM writes out lots of data - system 
becomes really unresponsive.


-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2009-11-19  6:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 21:45 Linux 2.6.31 - very swap-happy with plenty of free RAM Tomasz Chmielewski
2009-11-19  0:40 ` Dan Merillat
2009-11-19  1:09   ` Sven-Haegar Koch
2009-11-19  1:38     ` Dave Chinner
2009-11-19  6:43       ` Tomasz Chmielewski [this message]
2009-11-23 21:57         ` Dan Merillat
2009-11-27  1:56   ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2009-10-05  1:16 complete IO hang since a few kernel revision Norbert Preining
2009-11-18  7:56 ` Linux 2.6.31 - very swap-happy with plenty of free RAM Dan Merillat
2009-11-18 15:22   ` Rik van Riel
2009-11-18 15:48   ` Norbert Preining
2009-11-19 14:36   ` KOSAKI Motohiro
2009-11-25 23:13     ` Dan Merillat
2009-11-26  1:54       ` Rik van Riel
2009-12-03  4:16         ` Dan Merillat
2009-12-07 20:49           ` Dan Merillat
2009-12-09 20:48             ` Henrique de Moraes Holschuh
2009-12-09 21:18               ` Rik van Riel

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=4B04E8F6.3000004@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=dan.merillat@gmail.com \
    --cc=david@fromorbit.com \
    --cc=haegar@sdinet.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=preining@logic.at \
    --cc=riel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).