[En-Nut-Discussion] data sending delay

Harald Kipp harald.kipp at egnite.de
Fri Nov 5 11:05:33 CET 2004


Not really. The Nagle algorithm is hidden in the TCP stack
and "flushes" automatically after a specific time.

Your problem is related to simple stdio stream buffering
and appears on all stdio streams. However, Nut/OS is a bit
different. In order to avoid buffer copying, the stdio
routines do not use buffers. In Nut/OS all buffering is
done in the device driver only. Some devices, like devDebug0/1,
do not use any buffering at all and will provide immediate
output. Using devUsartAvr0/1 requires fflush() though.

Harald

At 01:52 05.11.2004 -0800, you wrote:
>Is it concern with something i came across called nagle algorithm?
>
>regards,
>helen
>
>Harald Kipp <harald.kipp at egnite.de> wrote:
>Hi Helen,
>
>most output devices in Nut/OS are buffered and require
>a flush. For streams use fflush().
>
>Harald
>
>At 17:48 04.11.2004 -0800, you wrote:
> >Hi,
> >my system communicates hardware and PC. I send 36 data in one frame only.
> >Why is that the data receive in my PC had a delay time? for example, the
> >PC shows the data of first frame only after i send more then ten frames?
> >How can i solve it?
> >
> >Thanks.
> >
> >regards,
> >helen




More information about the En-Nut-Discussion mailing list