lkml.org 
[lkml]   [2000]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Overcommittable memory
> >Write the program without recursion and you know at compile-time how
> >much memory it will ever need in the worst case.
> >There is always at least one page - so make sure you use less than that.
> >You'll need to know the stack overhead of any c-library you use - so
> >don't use it or figure it out. It is doable with open-source libraries.
>
> TBH, I don't see the point. I know I have more than enough RAM to
> handle most cases, and some extra swap for contingencies.
>
Someone mentioned how hard it was to write "memory safe" apps for
embedded
devices, considering how the stack is dynamically allocated. I pointed
out
that this isn't that hard.

Having enough RAM is fine for a pc. An embedded device running linux
will likely
be mass-produced with the minimum amount of RAM though.

Helge Hafting

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:57    [W:0.059 / U:2.244 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site