Re: Feature request: ability to use libeio with multiple event loops

2012-01-03 Thread Yaroslav
(4.1) Does TLS impose extra overhead (performance cost) compared to regular memory storage? Is it recommended to use in performance-concerned code? It requires an extra indirection. The app has to: 1. Figure out which thread it's currently running on. 2. Look up the location of the

Re: Feature request: ability to use libeio with multiple event loops

2012-01-03 Thread Brandon Black
On Tue, Jan 3, 2012 at 5:02 AM, Yaroslav yaro...@gmail.com wrote: Interesting observation: removing __thread storage class makes thread data shared by all threads. Even without any locks concurrent modifications of the same memory area result in 5-10 fold test time increase. I.e., shared

Re: Feature request: ability to use libeio with multiple event loops

2012-01-03 Thread Yaroslav
Yes, by concurrent modifications and shared variable write I mean concurrent writes. Not reads, of course. On Tue, Jan 3, 2012 at 5:48 PM, Brandon Black blbl...@gmail.com wrote: On Tue, Jan 3, 2012 at 5:02 AM, Yaroslav yaro...@gmail.com wrote: Interesting observation: removing __thread