[zeromq-dev] [PATCH] Scalability improvements for large amounts of connections

[gonzalo diethelm]

> >> For case 3 it should IMO either 'just work' when the socket is
created
> >> but never used in the parent thread (doing an implicit memory
barrier
> >> after creation, for example).
> >
> > +1
> 
> Does this mean 0MQ will do/does already do a memory barrier after
> creating a socket?

It might also be a good idea to mention a couple of examples of a memory
barrier call from C / C++.

-- 
Gonzalo Diethelm