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, an

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 o

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
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. Could the effects Peter mentions have anything

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

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

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

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

2003-09-07 Thread BRANE
- Original Message - From: "Peter Graf" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 08, 2003 12:05 AM Subject: Re: [ql-developers] Massive amount of job state transitions and re-scheduling > > BRANE wrote: > > >> Simple example: A M$ or Unix machine sends a fil

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 > e