ASU - out of memory?
tilman at baumann.name
Fri Aug 22 11:13:19 CEST 2008
I don't care for the warm and fuzzy feeling you get by having malloc
fail on you.
It does not give you a bit more system stability! The one app
receiving malloc errors is just not app of many. They all have a
Imagine, the browser catches a failed malloc, because some other
stupid app has eaten almost all ram.
What is the benefit of telling the browser about low mem? It could
only safe itself from crashing. Well done.
And malloc btw. never gives you bad memory. You just have to check,
even with overcommit.
It's just so that you have to be aware that the kernel who is watching
over all resources (the evil MCP muahahah)
may need to lay off some programms in a critical system condition.
No one wants this, so the strategy is to avoid this. We are talking
here about the same thing. We need some userspace helper to clean up
before it gets critical.
Yes, it sounds bad to have a error handling for out of memory and then
never use it.
Ask my mon, she will tell you this is horrible. But my mom does not
know the whole picture.
And once again. Not having overcommit wastes memory. Why do you think
this is worth it?
Ah, and btw. Nice analogy.
If you malloc (money alloc) some money at your bank they will give you
You know it is virtual value. You know they vastly overcommit.
You know, they will give you virtual money even if they can't know if
they can keep that promise?
Sounds horrible, doesn't it?
It kind of is. But they have swap too. And they try to fix it when
they become aware that there is a problem.
If you are lucky the banking kernel finds a solution. If not, we are
Come on, no one would ever do this! If they could not trust the paper
they get, how could they know if there is a problem?
It's a horrible system, let's go back to real values like gold...
No, we don't. See you at the bank. ;)
Am 22.08.2008 um 02:33 schrieb Carsten Haitzler (The Rasterman):
> On Thu, 21 Aug 2008 18:40:52 +0200 Tilman Baumann
> <tilman at baumann.name> babbled:
>> Not being able to malloc memory and not having any physical memory
>> are just two sepereate things. At least on modern linux systems.
> no they are not. i write code.
> myptr = malloc(mysize);
> it returns failuer (NULL) then i need to deal with it.
> it returns a pointer - it succeeded. i asked for memory - it gave it
> to me. the
> problem is with overcommit success returns are lies. they MAY have
> the memory -
> they may not. part way through using the pages it returned and SAID
> i could
> have, it can just segv - as it is overcommitted and out of pages.
> this means
> that suddenly return values can't be trusted for memory allocations
> any attempts to handle NULL returns may as well not exist as success
> cases can
> be undetectable failures. it's just a stupid policy. sure - its
> there to work
> around stupid userspace code that goes off allocing massive blobs of
> ram that
> it then never goes and uses, but the kernel should go punish all
> apps for this
> - those apps being stupid should be punished and have their code
>> Memory overcommit saves (physical) memory. And not just a bit.
>> And with some swap safety net it is reasonably save to do so.
>> And how should it be better if _any_ app gets knocked out by
>> running in
>> the memory limit? Usually it can't help the situation. Especially if
>> some other app that is eating all memory.
>> The effect is more or less the same. Some random poor app has to be
>> killed. (Since suicide is often the only way to react to malloc
>> Turning overcommit off is in my eyes only a poor 'bury one's head
>> in the
>> sand' solution which effectively does improve nothing.
> i disagree. overcommit is a "bury head in sand" solution. it means
> you just go
> and avoid the original problem of allocing much more memory than you
>> Overcommit and swap is just the winner. Everyone does it so. And in
>> eyes rightly so. It is fast and efficient.
>> And even without swap, i would not want to turn overcommit off.
>> Swap and overcommit is just the dream team. Fast and efficient
>> And if something goes wrong, you have plenty of time (and mem) for
>> solving the problem.
>> Contrary to without, because how could you fix any low memory
>> with not allocating any more memory? Driving something into swap to
>> able to do something about it is just right.
>> And just if you thought so. Overcommit is not just lazy don't care
>> errors behaviour but a really smart optimisation.
> wrong. it means i can no longer trust a successful malloc() calloc()
> or even alloca() return. ever. the return of a valid pointer which
> according to
> the manuals provided ever since for these calls, could be an error
> state too.
> and thew only way to handle it is have your own sigsegv/bus handlers
> and on a
> segv which accesses a known allocated chunk of memory, realise that
> just screwed you and try and save yourself (and frankly by this
> stage - you
> may as well just segv, exit or try re-exec yourself freshly).
> is is not elegant. it is not good. it is a cute hack that makes
> apps not impact things as much. it just sticks the head in the sand
> and doesn't
> go and fix the apps. it means the kernel tries to pick up the badly
> pieces for you and tends to punish all apps as a result.
>> For example it saves memory by only copying a page if the page was
>> written. (copy on write)
>> For example:
>> If you fork, the memory space is duplicated. You end up with twice
>> memory. But linux does not copy the memory, it overcommits.
>> Only if a page is really changed it get duplicated first.
>> This is elegant, fast and efficient. But yes, you loose the context
>> of a
>> error condition if some happens. But i say, if a system runs out of
>> memory, letting a program know that there is no memory left helps
>> nothing. The poor program that gehts the error is usually neither
>> to save much or even to solve the system wide problem.
>> Drucken Sie diese Mail bitte nur auf Recyclingpapier aus.
>> Please print this mail only on recycled paper.
> Carsten Haitzler (The Rasterman) <raster at openmoko.org>
> Openmoko community mailing list
> community at lists.openmoko.org
More information about the community