在每一时钟节拍，要制定调度决策的潜能。
At each tick, the potential for a scheduling decision is made.
该调用接收要运行的时钟节拍数作为其惟一的参数。
This call accepts as its only argument the number of ticks to run.
时钟计数功能：时钟节拍中断或从断电模式中唤醒。
Tick counter function: tick-interrupt or wake-up from power-off mode.
享受3令人兴奋的游戏模式：流行的顶部，时钟节拍，并击中了蛋！
Enjoy 3 exciting gameplay modes: Pop the Top, Beat the Clock, and Hit the Egg!
在一般的嵌入式实时操作系统中，时钟中断服务程序在每个时钟节拍工作。
In most RTOS, the timer interrupt service routine (ISR) executes at every time tick.
原来，当我们的内部时钟节拍加快以后，我们不但感知到外部世界的移动变慢了，我们实际上还可以记住更多的事情。
It turns out that when our internal clock is ticking faster, we don't just perceive the external world as moving slower - we can actually remember more about it.
此输出显示任务的列表（根据任务ID 编号）、其总执行时间（时钟节拍内）、等待执行的时间量以及调用的次数。
This output shows the list of tasks (numbered by task ID), their total execution time (in ticks), the amount of time they waited to execute, and finally the number of times they were invoked.
在实际应用中，并不是每个时钟节拍都有任务调度，所以有很多时钟中断服务程序的工作是多余的，浪费了CPU资源。
In most practical application, context switch doesn't happen at some time tick, so sometime the execution of timer ISR is useless and wastes CPU time.
最高优先级任务（精细值为 -20）收到大概 1200 亿个时钟节拍，而最低优先级任务（精细值为 19）接收到21,000,000 个时钟节拍。
The highest-priority task (nice of -20) received ~120 billion ticks, while the lowest-priority task (nice of 19) received 21 million ticks.
然后，它生成一个报告，列出这些代码单元每个获得了多少个“节拍(tick)”(即当代码的特定单元正在运行时发生了多少次系统时钟中断)。
Then it generates a report that lists how many "ticks" each of these units of code received (how many times a system-clock interrupt occurred when that particular unit of code was running).
时钟的节拍柔软无比。
时钟的节拍柔软无比。
应用推荐