From: Markku Savela <msa@moth.iki.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: Out of memory management in embedded systems
Date: Mon, 01 Oct 2007 10:58:24 +0300 [thread overview]
Message-ID: <87odfj5krj.fsf@burp.tkv.asdf.org> (raw)
In-Reply-To: <98Qu9-170-1@gated-at.bofh.it> (Abhishek Sagar's message of "Sat\, 29 Sep 2007 21\:50\:05 +0200")
How about just simple solution? Make it possible that "malloc" works
as it was originally intended: return NULL, if memory not available,
non-NULL only if allocation truly succeeded and is guaranteed..
Make kernel configuration option? (e.g. disable "over commit"
mis-feature :-)
--
Markku Savela
next prev parent reply other threads:[~2007-10-01 8:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98nC1-6aM-9@gated-at.bofh.it>
[not found] ` <98nVg-6QQ-21@gated-at.bofh.it>
[not found] ` <98oeB-7gA-9@gated-at.bofh.it>
[not found] ` <98oHC-8ai-5@gated-at.bofh.it>
[not found] ` <98oRk-8mt-21@gated-at.bofh.it>
[not found] ` <98pNu-1pp-17@gated-at.bofh.it>
2007-09-29 9:15 ` Out of memory management in embedded systems Bodo Eggert
[not found] ` <98v6u-1h1-9@gated-at.bofh.it>
[not found] ` <98Qu9-170-1@gated-at.bofh.it>
2007-10-01 7:58 ` Markku Savela [this message]
2007-10-01 8:13 ` Bernd Eckenfels
2007-10-01 16:27 ` david
2007-10-01 20:25 ` Robin Getz
2007-09-28 12:55 Daniel Spång
2007-09-28 13:09 ` linux-os (Dick Johnson)
2007-09-28 13:30 ` Daniel Spång
2007-09-28 14:04 ` linux-os (Dick Johnson)
2007-09-28 14:14 ` Daniel Spång
2007-09-28 15:16 ` linux-os (Dick Johnson)
2007-09-28 20:58 ` Daniel Spång
2007-09-29 19:48 ` Abhishek Sagar
2007-09-28 14:17 ` Rik van Riel
2007-09-28 14:36 ` Eric Dumazet
2007-09-28 15:15 ` Rik van Riel
2007-09-28 23:00 ` Nicholas Miell
2007-09-29 1:59 ` Daniel Phillips
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=87odfj5krj.fsf@burp.tkv.asdf.org \
--to=msa@moth.iki.fi \
--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.