Thomas.Doerfler at imd-systems.de
Thu Jul 22 17:44:26 UTC 2004
AFAIK tcp does packet gathering, so it tries to
collect several of your small written buffers to
make a more efficent "big" TCP packet (usually about
1.5KBytes). So in your case, I would expect that
about 150 write calls will result in one tcp packet
By the way, using a tool like "tcpdump" or
"ethereal" to analyze the network traffic might be
quite useful in this situation.
> ----- Original Message -----
> From: "Thomas Doerfler" <Thomas.Doerfler at imd-systems.de>
> To: "Stan" <zylog at club-internet.fr>
> Sent: Thursday, July 22, 2004 8:51 AM
> Subject: Re: TCP/IP problems
> > Hello Stan,
> > could you give a bit more details? how big is your
> > "buffer" and which value has "n" in your case? What
> > exactly happens at the other end of the TCP/IP
> > connection (Linux/Windows host)?
> > wkr,
> > Thomas.
> The 'buffer' is very small ( 22 bytes ) and write returns
> always 22 bytes.
> With Linux host, the number of bytes received is bigger than on
> Windows host.
> I missed a detail : if I take a period of 100 ticks between each write call,
> it works properly; ( performance is not terrible ;-) ).
> Since many weeks,I search and I don't understand this problem...
IMD Ingenieurbuero fuer Microcomputertechnik
Thomas Doerfler Herbststrasse 8
D-82178 Puchheim Germany
email: Thomas.Doerfler at imd-systems.de
PGP public key available at: http://www.imd-
More information about the users