All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Beck <mail@pierre-beck.de>
To: linux-kernel@vger.kernel.org
Subject: 3.6-rc7 32-bit PAE miscalculates dirty page limits
Date: Sun, 30 Sep 2012 11:38:45 +0200	[thread overview]
Message-ID: <5068130A.4050602@pierre-beck.de> (raw)

Hi,

there seems to be a bug in either ext4 or VM code triggered with 16 GB 
memory when compiled with 32-bit and PAE. dirty_background_ratio 
defaults to 10, dirty_ratio to 20. But in effect, dirty pages are 
strongly limited (zero or negative?). I observed extreme I/O wait states 
and slow disk access. A quick cure was to set dirty_bytes and 
dirty_background_bytes to sane values, overriding the ratios. An 
educated guess: the result of dirty_ratio calculation is stored as an 
unsigned 32-bit integer and overflows?

Greetings,

Pierre Beck

             reply	other threads:[~2012-09-30  9:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-30  9:38 Pierre Beck [this message]
2012-09-30 18:52 ` 3.6-rc7 32-bit PAE miscalculates dirty page limits H. Peter Anvin
2012-10-01 21:10   ` Pierre Beck
2012-10-01 21:52     ` Borislav Petkov
2012-10-01 21:53       ` H. Peter Anvin
2012-10-01 21:59         ` Borislav Petkov
2012-10-01 22:00           ` H. Peter Anvin

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=5068130A.4050602@pierre-beck.de \
    --to=mail@pierre-beck.de \
    --cc=linux-kernel@vger.kernel.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 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.