From: Eugene Surovegin <ebs@ebshome•net>
To: Martin Egholm Nielsen <martin@egholm-nielsen•dk>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Overcommit (OOM) problem on embedded device (PPChameleon)
Date: Tue, 29 Mar 2005 11:46:46 -0800 [thread overview]
Message-ID: <20050329194645.GA30850@gate.ebshome.net> (raw)
In-Reply-To: <4249ACF1.60305@egholm-nielsen.dk>
On Tue, Mar 29, 2005 at 09:30:57PM +0200, Martin Egholm Nielsen wrote:
[snip]
> Specs:
> I'm having an embedded Linux system running on a PPC405EP (PPChameleon)
> with 64 megs of RAM, some flash, but (ofcourse) no swap space. It runs a
> 2.4.20 kernel patched with drivers for my device.
>
> Problem:
> I have an application that is killed by the OOM (I guess) when it tries
> to "use" more memory than present on the system.
> Bolied down, memory is allocated with "sbrk" and then touch'ed (see
> test-application below).
[snip]
> However, both my desktop Linux (RH 7.3)/2.4.18-10/i386 and Linux
> (FC2)/2.6.5/i386 did what I expected:
Well, the only way to get the same results is to use the _same_ linux
kernel version and have the _same_ hw configuration (e.g. memory
configuration).
There were quite a few changes to VM during 2.4 lifetime; 2.6 is
different from 2.4 in the memory management area. RH kernel is
probably patched as hell, so who knows what VM it has.
--
Eugene
next prev parent reply other threads:[~2005-03-29 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 19:30 Overcommit (OOM) problem on embedded device (PPChameleon) Martin Egholm Nielsen
2005-03-29 19:46 ` Eugene Surovegin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-30 10:30 Per Hallsmark
2005-03-31 6:50 ` Martin Egholm Nielsen
2005-03-31 8:23 ` Martin Egholm Nielsen
2005-03-31 16:15 ` David Adair
2005-03-31 20:13 ` Martin Egholm Nielsen
2005-04-01 9:58 ` Martin Egholm Nielsen
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=20050329194645.GA30850@gate.ebshome.net \
--to=ebs@ebshome$(echo .)net \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=martin@egholm-nielsen$(echo .)dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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