Subject: Re: [boost] [log] Is it lock free ?
From: adrien courdavault (adrien.courdavault_at_[hidden])
Date: 2013-04-30 02:48:29
Yes that is what worried me, I can't have any operation like lock or
classic malloc in my thread.
I could use a specific allocator for preallocation,
But I would more need a queue like LockFree. and it would obviously be
I know that the consequences (problem of message ordering, limis in
message rate because of the no allocation on the source side)
But that would realy be what I need.
Thank you for your answers
On 30 April 2013 05:41, Andrey Semashev <andrey.semashev_at_[hidden]> wrote:
> On Tuesday 30 April 2013 07:32:06 you wrote:
>> asynchronous_sink<T, unbounded_fifo_queue> uses a lock-free queue
>> internally, so it will avoid locking.
> Ughh, I just remembered there is also a lock in this case, so technically it's
> not lock-free either. Sorry.
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk