On tor, 2008-05-15 at 16:11 +0200, Jan Safranek wrote:
> Magnus Fromreide wrote:
> > Do the rewrite affect both stream and packet sockets or only stream
> > sockets?
>
> Currently both, but if there will be flag allowing asynchronous write,
> like hardaker is suggesting,
Magnus Fromreide wrote:
> Do the rewrite affect both stream and packet sockets or only stream
> sockets?
Currently both, but if there will be flag allowing asynchronous write,
like hardaker is suggesting, I'll have to rewrite it either.
> What action should be taken if the remote
> On Wed, 14 May 2008 15:03:37 +0200, Jan Safranek <[EMAIL PROTECTED]> said:
JS> net-snmp by default expects that send() on a socket always send whole
JS> provided buffer and is blocking. This leads to deadlocks under heavy
JS> load - see bug #1598344.
Interesting findings and good work!
M
On ons, 2008-05-14 at 15:03 +0200, Jan Safranek wrote:
> Hi,
>
> net-snmp by default expects that send() on a socket always send whole
> provided buffer and is blocking. This leads to deadlocks under heavy
> load - see bug #1598344.
>
> I'm rewriting the snmp_api so the write will be asynchrono
Hi,
net-snmp by default expects that send() on a socket always send whole
provided buffer and is blocking. This leads to deadlocks under heavy
load - see bug #1598344.
I'm rewriting the snmp_api so the write will be asynchronous and
non-blocking. It seems to me that the session API is somehow
