Peter Graf writes:
> >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
Peter Graf writes:
> Hi Per,
>
> >And Peter, did you try out the suggestions that were made at that time?
>
> Can you be a bit more specific? I remember only one applicable suggestion,
> which was to set a system variable before leaving the ISR. Didn't work, at
> least not under QDOS.
# By exiti
On 12 Sep 2003 at 13:00, BRANE wrote:
> O.K. I'm not following this thread from beginning, so I don't know exactly
> what hardware are we talking about, but for this detail, it probably doesn't
> matter much...
>
> So, what is a solution ? Using external interrupt ? Maybe a bit bulkier
> control
>
> don't forget this is a rather simple TCP/IP implementation and apparently
> it is already hard enough to make the simplest variant working reliably
> with the garden variety of TCP/IP implementations out there.
>
> Richard
O.K. I'm not following this thread from beginning, so I don't know exa
On Sun, Sep 07, 2003 at 10:48:50PM +0200, BRANE wrote:
>
>
> - 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
>
On 8 Sep 2003 at 1:03, BRANE wrote:
> > QLwIP offers a window of 8760, but I have found that neither Windows nor
> > Linux will exploit that in their standard configuration, at least not as
> > long as their counterpart has 20 ms latency. Depending on the application,
> > they send one, maximum t
