> On 23 Jan 2004, Don Lewis wrote:
> > the send does not give an error: the packet is just thrown away.
>
> Which is the same result as you would get if the bottleneck is just one
> network hop away instead of at the local NIC.
But it isn't. I'm broadcasting onto the local network. With Linux an
> send() for UDP should block if the socket is filled and the interface
> can't drain the data fast enough.
It doesn't (at least I cannot make it block)
> Good question. There is not feedback loop like in tcp, so handling this
> blocking and releasing would be a little bit harder to do for UDP.
The documentation for send(2) says
If no messages space is available at the socket to hold the message to be
transmitted, then send() normally blocks, unless the socket has been
placed in non-blocking I/O mode. The select(2) call may be used to
determine when it is
The documentation for send(2) says
If no messages space is available at the socket to hold the message to be
transmitted, then send() normally blocks, unless the socket has been
placed in non-blocking I/O mode. The select(2) call may be used to
determine when it is
4 matches
Mail list logo
