Re: Seeing large amounts of data on udp recv-q, only sending 1 byte of data
- From: David Schwartz <davids@xxxxxxxxxxxxx>
- Date: 25 May 2007 08:44:32 -0700
On May 25, 4:36 am, "ssuss...@xxxxxxxxxxxxxxxxxxx" <s...@xxxxxxxxxxx>
wrote:
I had that thought as well, but even the headers wouldn't account for
the extra data.
IP Hdr - 20 bytes
UDP Hdr - 8 bytes
payload - 1 byte
272-29 = 243 bytes remaining.
also if I up the payload to 10 bytes the amount of data on the recv
queue doubles to 544 bytes. The amount of overhead data should not
increase with a minimal amount of payload increases.
You would have to look at the specifics of how your particular
operating system stores datagrams internally. Many of them have a
surprisingly large amount of additional information that they store
along with the data. There is no generic way to figure out how much
input queue space a particular datagram will take.
Oddly, even for TCP data, some kernels allocate control structures and
count them against the receive buffer. The receive buffer is measured
in bytes, but what counts as a byte is far from clear.
DS
.
- References:
- Seeing large amounts of data on udp recv-q, only sending 1 byte of data
- From: ssussman@xxxxxxxxxxxxxxxxxxx
- Re: Seeing large amounts of data on udp recv-q, only sending 1 byte of data
- From: David Schwartz
- Re: Seeing large amounts of data on udp recv-q, only sending 1 byte of data
- From: ssussman@xxxxxxxxxxxxxxxxxxx
- Seeing large amounts of data on udp recv-q, only sending 1 byte of data
- Prev by Date: Re: Seeing large amounts of data on udp recv-q, only sending 1 byte of data
- Next by Date: Re: Multiple ethernet interfaces generated
- Previous by thread: Re: Seeing large amounts of data on udp recv-q, only sending 1 byte of data
- Next by thread: WIreless client cannot get ip
- Index(es):
Relevant Pages
|