Re: Bug in log.c
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | Wapme Systems AG |
| Message-ID | <[email protected]> |
> how about having this inside gwthread-pthread.c as function:
>
> /* Return the threadtable sloot this thread is using. */
> long gwthread_table_slot(void)
> {
> return (gwthread_self() % THREADTABLE_SIZE);
> }
>
> and use this call instead of gwthread_self() for the logging
> functions?!
how much performance impact would a function call have this way
instead of doing it directly inside the logging functions?!
Anyone having C performance experience here?
Stipe
[email protected]
-------------------------------------------------------------------
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [email protected]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are