Re: question about thread scheduling

Hi Remi,
thanks for your advice.
Let me tell you what I exactly want to do:

In essential, it is a control problem, and I must send a voltage to the
moter every 4ms(this can be configured to another value in other cases), and
this voltage is calculated through a process model, which is based on neural
network. During the 4ms, I must use the CUP resource as much as possible,
since algorithms on neural networks are always computational intensive, and
I have to stop my calculation before is reach the 4ms deadline, so I am
afraid that I can not use any sleep function to kill the precious CPU time:)

I am using CE 6.0 on a CEPC, and I have modifid the value of
g_dwBSPMsPerIntr to 4, so that it will generate an timer interrupt every
4ms. I found that if I want to let the scheduler run also every 4ms, I have
to modify the code inside "PeRPISR", so that it will generated a
SYSINTR_RESCHED every 4ms.

I am now study this source code, and trying to modify it to meet my
requirement.

best wishes
Zhiqiang
"Remi de Gravelaine" <gravelaine at aton dash sys dot fr> schrieb im
Newsbeitrag news:OHk45G9ZHHA.4520@xxxxxxxxxxxxxxxxxxxxxxx
Zhiqiang,

You should try to tell us *exactly* what you want to do.
You should also avoid multiplying the discussion threads if you want
people to take care of you from the beginning.
If I understood what you want to do, you have implemented a polling loop
to do some job (what kind of job?) every 4ms.
You have put this loop in a high-priority thread started by the XXX_Init
function of a stream driver.
You are using CE 6.0 on a CEPC.

The loop should thus look like:

while (!g_bSuicide)
{
Sleep(3);
<do some job>
}

There is no reason that such a loop exits except when g_bSuicide is set to
TRUE (something that can be done in XXX_Deinit) or the <do some job> code
executes a break of goto intruction.

Now, why Sleep(3) instead of Sleep(4)? Because Sleep(3) will sleep for *at
least* 3 ms and because Sleep is synchonized on timer ticks, that fire
every ms (producing the SYSINTR_RESCHED you are focusing on.) So, Sleep(3)
returns from sleeping right after the third tick and a new 1ms slice
begins. You <do some job> during a portion of this slice and reenter
Sleep(3). Sleep(3) puts your thread to sleep for 3 timer ticks and that
means the time remaining in the current tick + 3 ms.

HTH
Remi



.

Relevant Pages

  • Re: question about thread scheduling
    ... You have put this loop in a high-priority thread started by the XXX_Init ... You during a portion of this slice and reenter ... means the time remaining in the current tick + 3 ms. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: question about thread scheduling
    ... I realize that I have misunderstood what you have told me. ... You have put this loop in a high-priority thread started by the XXX_Init ... Sleepreturns from sleeping right after the third tick and a new 1ms ... slice begins. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: PID question
    ... An analog input on the micro will monitor load current. ... controlling the set voltage. ... Since you are dealing with a loop you should analyse it ... Ki is an integrator which means its response falls at 20dB/decade and it has ...
    (sci.electronics.design)
  • Re: question about thread scheduling
    ... I doubt you will need to mess with the system tick to get what ... I will try what you suggested, the reason that I didn't use the sleep ... If the NN run in a different thread as the control loop ... Sleepputs your thread to sleep for 3 timer ticks and ...
    (microsoft.public.windowsce.platbuilder)
  • Re: How a Telephone Works
    ... the telco has to apply DC bias voltage and AC ring ... This voltage causes a direct current to flow in the loop. ... channels, often on two copper pairs, at 1.544 Mbps. ...
    (comp.dcom.telecom)