----- Original Message ----- 
From: "Peter Graf" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 07, 2003 9:53 PM
Subject: Re: [ql-developers] Massive amount of job state transitions and
re-scheduling


>
> Thierry wrote:
>
> >Yes, this I know, thanks... I'm perfectly aware of the fragmentation and
of
> >out of order receipt of TCP packets... That doesn't change the fact you
could
> >use the fast interrupt to store as many TCP packet as needed (i.e. when
they
> >come in), into a buffer (organized as a linked list of recieved packets),
> >then to transfer the whole lot of packets to the higher level layers of
the
> >TCP/IP stack at once and every 1/50th of second...
>
> Obviously correct but useless. Try to understand that the problem in your
> approach is latency and can not be solved by buffering, no matter how
> efficient buffering is implemented.
>
> Simple example: A M$ or Unix machine sends a file to the QDOS machine via
> TCP. It will send one or two packets, then stop and wait for ACK. Further
> packets will only be sent after further ACKs. Your ACKs can only be
> generated in 50 Hz rhythm, so packets will crawl one-by-one in 50 Hz
> rhythm. (Or two-by-two, if you're lucky.)

AFAIK with TCP/IP this is negotiable. There is no need for such small
window...


Reply via email to