[Click] dynamic memory allocation

[Eddie Kohler]

> Which brings me to my question, is there a way in Linux to determine the 
> current available non-paged memory ? I've run into issues before where OOM 
> errors resulted in undesirable crashes even with checking pointers after 
> memory allocation. I'm thinking about an element early on in the 
> configuration that checks for available memory and if a threshold has been 
> reached will by-pass most of the configuration and only do necessary 
> forwarding.

/proc/meminfo?

Eddie


> 
> Beyers
> 
> On 09 Sep 2005 13:32:27 +0000, Alastair McKinley <amckinley03 at qub.ac.uk> 
> wrote:
> 
>>Hi,
>>
>>I have a patch here to display the current dynamic memory allocation with
>>kernel click. It works with CLICK_DMALLOC enabled. This is my first 
>>attempt
>>at delving into the Click source, so please humour me!
>>
>>Patch is attached and is against Click 1.4.3, I'm having trouble getting
>>current CVS.
>>
>>Regards,
>>
>>Alastair
>>
>>
>>
>>_______________________________________________
>>click mailing list
>>click at amsterdam.lcs.mit.edu
>>https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>>
>>
>>
>>
> 
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>