public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Mikael Pettersson <mikpelinux@gmail.com>,
	Andreas Schwab <schwab@linux-m68k.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [3.13 regression] kswapd0 and ksoftirqd/0 CPU hogs
Date: Tue, 07 Apr 2015 09:25:41 +1200	[thread overview]
Message-ID: <5522F9D5.3080107@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1504011533340.23336@nippy.intranet>

Hi Finn,

> On Wed, 1 Apr 2015, Michael Schmitz wrote:
>
>   
>> I've followed the vm stats while running gunzip -c on a large file. I 
>> get an 'invalid compressed data' error at the very end of the gunzip 
>> run, and the file md5sum does not match what I get when uncompressing 
>> that file on another system with no error
>>     
>
> Was that an aranym virtual machine or a physical one? If physical, can the 
> error be reproduced using a virtual one (given same RAM size, kernel etc)?
>   

The gunzip error cannot be reproduced on any of my ARAnyM VMs. Might be 
a RAM error or other hardware related problem. Same kernel but 
configured slightly different (added 030 and 040 support, plus ARAnyM 
support).

The general behaviour (gunzip eats up all free RAM, then kswapd spins 
doing nothing very apparent, with no dirty pages to be flushed and 
cached pages never released) remains the same. Though I've seen the 
gunzip complete without kicking off kswapd on occasion (had set 
dirty_background_ratio and dirty_ratio half the default for that).

And yes, dropping cached pages as Andreas suggested, does free up 
significant (i.e. most of all) RAM and shuts up kswapd.

    Michael

  parent reply	other threads:[~2015-04-06 21:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 11:38 [3.13 regression] kswapd0 and ksoftirqd/0 CPU hogs Mikael Pettersson
2014-06-06 11:43 ` Geert Uytterhoeven
2014-06-06 13:11   ` Mikael Pettersson
2014-06-07 13:22     ` Mikael Pettersson
2014-06-11  8:20       ` Mikael Pettersson
2014-06-11  8:45 ` Andreas Schwab
2014-07-01 11:43   ` Mikael Pettersson
2015-03-31  1:16     ` Michael Schmitz
2015-03-31 13:19       ` Mikael Pettersson
2015-04-01  3:08         ` Michael Schmitz
2015-04-01  4:45           ` Finn Thain
2015-04-01  5:21             ` Michael Schmitz
2015-04-06 21:25             ` Michael Schmitz [this message]
2015-04-07  0:06               ` Finn Thain
2015-04-07  5:38                 ` Michael Schmitz
2016-02-21 17:06         ` Mikael Pettersson
2016-02-21 19:31           ` Michael Schmitz
2016-02-22 10:01           ` Geert Uytterhoeven
2016-03-06  7:21             ` Mikael Pettersson
2016-03-06  8:54               ` Geert Uytterhoeven
2016-03-06  9:20                 ` Mikael Pettersson
2016-04-13 18:57                   ` Mikael Pettersson
2016-05-31  4:52           ` Finn Thain
2016-05-31 10:06             ` Mikael Pettersson
2016-05-31 10:21               ` Geert Uytterhoeven
2016-05-31 10:39                 ` John Paul Adrian Glaubitz
2016-05-31 10:41                   ` Geert Uytterhoeven
2016-06-01  6:36                 ` Mikael Pettersson
2015-04-01 16:11       ` Andreas Schwab

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=5522F9D5.3080107@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=fthain@telegraphics.com.au \
    --cc=linux-m68k@vger.kernel.org \
    --cc=mikpelinux@gmail.com \
    --cc=schwab@linux-m68k.org \
    /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