Feature request: ability to use libeio with multiple event loops

Yaroslav yarosla at gmail.com
Tue Jan 3 15:26:55 CET 2012


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 <blblack at gmail.com> wrote:

>
>
> On Tue, Jan 3, 2012 at 5:02 AM, Yaroslav <yarosla at 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 variable write is about 5-10 times slower than non-shared even
>> without any locks.
>>
>
> I assume you mean concurrent writes of course.  Implicitly shared memory
> between threads should have regular access time when there's no false
> sharing with other threads writing to nearby memory.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schmorp.de/pipermail/libev/attachments/20120103/29f9e700/attachment-0001.html>


More information about the libev mailing list