Re: [Libunwind-devel] Updated fast trace patch with initial performance results

[Arun Sharma]

On Mon, Apr 4, 2011 at 10:45 PM, Lassi Tuura <address@hidden> wrote:

> All clear from me to use __thread. I originally used it, but changed because 
> include/libunwind_i.h says:
>
>   38 #ifdef HAVE___THREAD
>   39   /* For now, turn off per-thread caching.  It uses up too much TLS
>   40      memory per thread even when the thread never uses libunwind at
>   41      all.  */
>   42 # undef HAVE___THREAD
>   43 #endif
>
> I meant to ask if someone could expand on that comment? I thought it wouldn't 
> apply to the fast trace, which could use __thread, but I am not familiar 
> enough with __thread implementations out there to know what triggered that 
> comment so I backed off.
>

The intent of the comment I thought was to say per-thread caches
consume more memory than global caches, regardless of the TLS
implementation details.

 -Arun