configure ACK delay for TCP

[Eric Norum]

I don't understand what you're suggesting.   The event is sent by the interrupt handler when a packet is received.   If no packet has been received I don't see any advantage in waking up the receive thread after every clock tick.   

Which driver in particular are you describing?

On Jun 8, 2010, at 5:58 AM, Wolfgang Rostek wrote:

> Hi group 
> 
> I'm testing my RTEMS socket server application and run into problems with a fast client. 
> 
> Tracking down the problem seems to arise from a default ACK delay of 200 ms for TCP. 
> 
> From within my network.c it seems that the fec rx daemon should not invoke 
> 
>     rtems_bsdnet_event_receive (INTERRUPT_EVENT | FATAL_INT_EVENT, 
>         RTEMS_WAIT | RTEMS_EVENT_ANY, 
>         RTEMS_NO_TIMEOUT, &events);
> 
> this way. 
> 
> To get an immediate ACK is it correct to replace RTEMS_NO_TIMEOUT by '1' or 
> is there another location to setup ACK handling for TCP? 
> 
> thanks
> Wolfgang Rostek
> 
> Phone: +49 (89) 92 16-2183
> Fax: +49 (89) 92 16-162183
> http://www.esg.de
> ESG Elektroniksystem- und Logistik-GmbH
> 82256 Fuerstenfeldbruck, Livry-Gargan Str. 6, Germany_______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users

-- 
Eric Norum
wenorum at lbl.gov

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20100608/db537a9f/attachment-0001.html>