On Mon, 26 Jan 2004, Steve Watt wrote:
[EMAIL PROTECTED] wrote:
do what ping does (ping -f)
when you get an ENOBUFS do a usleep for 1 mSec.
and then send it again.
So how, exactly, do you actually sleep for 1mSec? I recently did some
experiments using nanosleep(), and it seems that the
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 and
do what ping does (ping -f)
when you get an ENOBUFS do a usleep for 1 mSec.
and then send it again.
On Mon, 26 Jan 2004, Stuart Pook wrote:
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
On Mon, Jan 26, 2004 at 10:53:54AM -0800, Julian Elischer wrote:
...
On Mon, 26 Jan 2004, Stuart Pook wrote:
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
[EMAIL PROTECTED] wrote:
do what ping does (ping -f)
when you get an ENOBUFS do a usleep for 1 mSec.
and then send it again.
So how, exactly, do you actually sleep for 1mSec? I recently did some
experiments using nanosleep(), and it seems that the minimum sleep time
is 2 / HZ. I.e. ask for
On Mon, 26 Jan 2004, Steve Watt wrote:
[EMAIL PROTECTED] wrote:
do what ping does (ping -f)
when you get an ENOBUFS do a usleep for 1 mSec.
and then send it again.
you are correct, but I just meant that it requested to sleep 1mSec, not
that the sleep actually WAS 1mSec.
Making udp sockets
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
Stuart Pook wrote:
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
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.
On Fri, Jan 23, 2004 at 04:25:07PM +0100, Stuart Pook wrote:
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.
Stuart Pook wrote:
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)
This stuff is rather complex. A send() on a UDP socket processes right
down to the if_output. If that fails because the ifqueue
On Fri, Jan 23, 2004 at 06:09:20PM +0100, Andre Oppermann wrote:
...
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)
This stuff is rather complex. A send() on a UDP socket processes
On Fri, 23 Jan 2004, Andre Oppermann wrote:
Stuart Pook wrote:
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)
This stuff is rather complex. A send() on a UDP socket processes right
On 23 Jan, Stuart Pook wrote:
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
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
On Monday, January 19, 2004, at 08:53 AM, Stuart Pook wrote:
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
16 matches
Mail list logo
