Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-08 Thread Richard Zidlicky
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 Simple

Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-08 Thread BRANE
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 exactly

Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-08 Thread pgraf
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 controller

Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-08 Thread P Witte
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 exiting the

Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-07 Thread P Witte
Richard Zidlicky writes: Plus, I'm a bit surprised that you are apparently using jobs to fetch the data from the ethernet card... It should be done via an interrupt handler instead... Actually, the best design would be to have the Q60 fast interrupt handler to fill a buffer, and a frame

Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-07 Thread Thierry Godefroy
On Sat, 06 Sep 2003 00:24:18 +0200, Peter Graf wrote: Thierry wrote: .../... Plus, I'm a bit surprised that you are apparently using jobs to fetch the data from the ethernet card... It should be done via an interrupt handler instead... At first sight it looks like that of course.

Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-07 Thread Peter Graf
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

Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-07 Thread Peter Graf
BRANE wrote: 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

Re: [ql-developers] Massive amount of job state transitions and re-scheduling

2003-09-07 Thread BRANE
- Original Message - From: BRANE [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 08, 2003 1:03 AM Subject: Re: [ql-developers] Massive amount of job state transitions and re-scheduling Besides, I find it a bit hard to believe that average PC does acknowledge every