![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Two things: 1.> There is the possibility that it is not actually malloc'd, but just 'reserved' by the system - I must admit that I am not entirely clear on this aspect of how top reports memory usage, but I have heard something about this before. Try Google. 2.> I know I have read alot of recommendations to, if you can, write your own memory allocation. Most of these were from people I would consider knowledgable, but I must admit I myself have never felt inclined to do it. I do believe that these recommendations were made on the premise that the author didn't trust the generally available memory allocation that come with most compilers. My 2 cents, Grant M. -- ====================================== Grant M. NAPC Support New American Platinotype Company, Inc. (781)894-3114 x240 "Celebrating our 11th year!"
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |