[zeromq-dev] HWM default

[Paul Colomiets]

On Mon, May 9, 2011 at 9:17 AM, Blair Bethwaite
<blair.bethwaite at monash.edu>wrote:
>
>
> As an aside, any idea of the 0MQ behaviour under flooding with no HWM
> but sane kernel virtual memory settings (i.e.,
> /proc/sys/vm/overcommit_memory=2)...?
>
>
Well, I have no practical experience, but a lot of alloc_assert's in the
code says that it will be aborted. BTW, it will be so not only if
overcommit_memory is set right, but also if ulimit is set for the
application's memory. Which is awfully bad IMO.

 We should distinguish deadlocks inside 0MQ (such as one introduced by the
> shutdown functionality) which should be considered 0MQ bugs and deadlocks in
> applications on top of 0MQ (the ones we are discussing now) which should be
> considered application bugs.


Don't see why shutdown would introduce deadlocks inside 0mq

But thinking of it a bit more about default HWM, it seems that issues are
same using TCP or unix domain sockets. And for future in-kernel
implementation HWM should probably always be set. So it's probably ok to
have reasonable default.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20110509/6ddc1ae3/attachment.htm>