frasc wrote: > ________ ________ ________ > Interrupt ______| |______| |______| |____ > . > . ________ ________ ________ > Pin 2 ______.__| |______| |______| |____ > . . . > . . _____.__ ________ ________ > Pin 3 ______.__.__| . |______| |______| |____ > . . . . > . . . . > t0 t1 > > `t0' will be the interrupt latency. this topic has already been discussed > quite a bit on this list > > `t1' would be the `schedulaer latency' [a better name someone ?] which I'd > like to caracterize. > > The values I got so far for `t1' are in the range: 19.6-25 usecs. How about "scheduler context switching time/delay/latency" ? Brendan Simon.
begin:vcard n:Simon;Brendan tel;fax:+61 3 9886 0269 tel;home:+61 3 9561 0817 tel;work:+61 3 9886 0128 x-mozilla-html:TRUE org:CTAM Pty Ltd adr:;;469 Springvale Rd;Glen Waverly;Victoria;3150;Australia version:2.1 email;internet:[EMAIL PROTECTED] title:Embedded Systems Design Engineer x-mozilla-cpt:;-7584 fn:Brendan Simon end:vcard
