All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wesley <awesley@acquerra.com.au>
To: nate.diller@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.13 buffer strangeness
Date: Sat, 10 Sep 2005 15:32:10 +1000	[thread overview]
Message-ID: <43226FDA.4070607@acquerra.com.au> (raw)
In-Reply-To: <5c49b0ed05090922021b8f8112@mail.gmail.com>

Nate Diller wrote:
> just found the culprit.  guess i should have read the code the first 
> time.  get_dirty_limits() in drivers/block/page_writeback.c has a 
> hard-coded upper limit to dirty_ratio.  it's capped to half of the 
> unmapped pages, so maybe 30-40% of your system's memory.  so if you are 
> brave, just remove the "/ 2" parts from the 'if (dirty_ratio > 
> unmapped_ratio / 2) dirty_ratio = unmapped_ratio / 2;' check, and you 
> can have all the OOM goodness you want.

Excellent. OOM here I come.

> i really recommend you focus on getting better disk bandwidth, you stand 
> to gain a lot more from that approach.  i presume you're on ext3; 
> perhaps you should try reiser4 or xfs, they are more likely to meet your 
> disk bandwidth requirements.

Yep, pursuing this as well, also looking to add more RAM to the machine. At this stage
I was just trying to understand the numbers that I was seeing, so I could work out the
best way to proceed.

I'm using ext2 at the moment, on the assumption that the journal would cost 
me a bit of performance so I left it out :-)

I'll certainly try the other filesystems as you suggest.

Thanks again, Anthony

-- 
Anthony Wesley
Director and IT/Network Consultant
Smart Networks Pty Ltd
Acquerra Pty Ltd

Anthony.Wesley@acquerra.com.au
Phone: (02) 62595404 or 0419409836

  parent reply	other threads:[~2005-09-10  5:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09  9:11 kernel 2.6.13 buffer strangeness Anthony Wesley
2005-09-09 15:09 ` Roger Heflin
2005-09-09 21:39   ` Nate Diller
2005-09-10  0:16     ` Anthony Wesley
2005-09-10  0:35       ` Nate Diller
2005-09-10  1:07         ` Anthony Wesley
2005-09-10  1:47           ` Nate Diller
2005-09-10  2:23             ` Anthony Wesley
     [not found]               ` <5c49b0ed05090922021b8f8112@mail.gmail.com>
2005-09-10  5:32                 ` Anthony Wesley [this message]
2005-09-10  6:02                 ` kernel 2.6.13 buffer strangeness - FIXED Anthony Wesley
2005-09-10 10:23                 ` kernel 2.6.13 buffer strangeness - ext2/3/reiser4/xfs comparison Anthony Wesley
2005-09-10 11:42                   ` Andrew Morton
2005-09-10 11:56                     ` Anthony Wesley
2005-09-10  0:50     ` kernel 2.6.13 buffer strangeness Anthony Wesley
2005-09-10  5:41       ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2005-09-09  8:14 Anthony Wesley
2005-09-09  8:24 ` David Lang

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=43226FDA.4070607@acquerra.com.au \
    --to=awesley@acquerra.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nate.diller@gmail.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.