LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: tuning/tweaking VM settings for low memory (preventing OOM)
Date: Fri, 12 Jan 2007 15:58:08 -0600	[thread overview]
Message-ID: <D7BBB18A-F5D4-4FE0-903F-3683333D957C@kernel.crashing.org> (raw)

I'm working on an embedded PPC setup with 64M of memory and no swap.   
I'm trying to figure out how best to tune the VM for an OOM situation  
I'm running into.

I'm running a 2.6.16.35 kernel and have a bittorrent app that appears  
to be initializing a large file for it to download into.  What I see  
before running the app:

/bigfoot/usb_disk # cat /proc/meminfo
MemTotal:        62520 kB
MemFree:         49192 kB
Buffers:          8240 kB
Cached:            740 kB
SwapCached:          0 kB
Active:           8196 kB
Inactive:         1236 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:        62520 kB
LowFree:         49192 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
Mapped:            916 kB
Slab:             2224 kB
CommitLimit:     31260 kB
Committed_AS:     1704 kB
PageTables:         88 kB
VmallocTotal:   933872 kB
VmallocUsed:      9416 kB
VmallocChunk:   923628 kB

after the OOM:

/bigfoot/usb_disk # cat /proc/meminfo
MemTotal:        62520 kB
MemFree:          1608 kB
Buffers:          8212 kB
Cached:          42780 kB
SwapCached:          0 kB
Active:           6228 kB
Inactive:        45176 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:        62520 kB
LowFree:          1608 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:           35208 kB
Writeback:        5616 kB
Mapped:            892 kB
Slab:             7788 kB
CommitLimit:     31260 kB
Committed_AS:     1704 kB
PageTables:         88 kB
VmallocTotal:   933872 kB
VmallocUsed:      9416 kB
VmallocChunk:   923628 kB

Which makes me think that we aren't writing back fast enough.  If I  
mount the drive "sync" the issue clearly goes away.

It appears from an strace we are doing ftruncate64(5, 178257920) when  
we OOM.

Any ideas on VM parameters to tweak so we throttle this from occurring?

- k

             reply	other threads:[~2007-01-12 21:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 21:58 Kumar Gala [this message]
2007-01-13  4:54 ` Nick Piggin
2007-01-15 17:13   ` Kumar Gala
2007-01-13  7:22 ` Willy Tarreau
2007-01-13 13:16   ` Toon van der Pas
2007-01-13 14:30     ` Willy Tarreau
2007-01-13 23:58       ` Toon van der Pas

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=D7BBB18A-F5D4-4FE0-903F-3683333D957C@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: tuning/tweaking VM settings for low memory (preventing OOM)' \
    /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

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).