* [ECOS] Is clock interrupt = tick ?
@ 2001-04-19 10:28 Huang Qiang
2001-04-19 15:03 ` Jonathan Larmour
0 siblings, 1 reply; 2+ messages in thread
From: Huang Qiang @ 2001-04-19 10:28 UTC (permalink / raw)
To: eCos
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ECOS] Is clock interrupt = tick ?
2001-04-19 10:28 [ECOS] Is clock interrupt = tick ? Huang Qiang
@ 2001-04-19 15:03 ` Jonathan Larmour
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Larmour @ 2001-04-19 15:03 UTC (permalink / raw)
To: Huang Qiang; +Cc: eCos
[ Is clock interrupt = tick? ]
It may depend on your terminology. Most hardware clocks have an internal
counter, often a resetting decrementer which you program to trigger an
interrupt when it hits zero.
It's up to you whether you consider the change in the value of the
decrementer to be a tick, or the clock interrupt to be a tick. My
preference is for the latter, and I think that is definitely the most
common usage. So in short, yes :-).
But note that kernel timeslicing doesn't take place every clock interrupt -
it actually happens according to the eCos CDL option
CYGNUM_KERNEL_SCHED_TIMESLICE_TICKS, which defaults to 5 ticks between
reschedules.
Jifl
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-04-19 15:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-04-19 10:28 [ECOS] Is clock interrupt = tick ? Huang Qiang
2001-04-19 15:03 ` Jonathan Larmour
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).