Re: ls: can't open '.': Cannot allocate memory

Quoth Larry Baker:
> I've tried those solutions too -- no good.  I decided that was 
> because those are kernel memory allocation policies, and have no 
> effect on user memory allocation.  Is that correct?

Not entirely.  User-mode malloc typically requests a chunk of memory from
the kernel (which is subject to kernel allocation policies) and then
subdivides this internally for further requests (from the same process
only).  This does mean that with each new process started a bit of memory
becomes unavailable to other processes until they exit; depending on the
pattern of new processes starting and how much memory they're allocating
this can lead to fragmentation.

The precise details vary a bit depending on which libc you're using and how
you have it configured.


_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev