Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1492614 > unrolled thread
| Started by | gengdongjiu <gengdj.1984@gmail.com> |
|---|---|
| First post | 2016-09-28 16:00 +0200 |
| Last post | 2016-09-28 16:00 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Fwd: Delivery Status Notification (Failure) gengdongjiu <gengdj.1984@gmail.com> - 2016-09-28 16:00 +0200
| From | gengdongjiu <gengdj.1984@gmail.com> |
|---|---|
| Date | 2016-09-28 16:00 +0200 |
| Subject | Fwd: Delivery Status Notification (Failure) |
| Message-ID | <smnyV-7th-7@gated-at.bofh.it> |
Hi,
In the kernel 4.1, I am confused for the
runnable_avg_sum/avg_period/running_avg_sum,
for example below code.
Does the task runnable_avg_sum includes running_avg_sum? Does avg_period
includes the task runnable_avg_sum and the task sleep time? thank you.
static inline void __update_task_entity_contrib(struct sched_entity *se)
{
u32 contrib;
/* avoid overflowing a 32-bit type w/ SCHED_LOAD_SCALE */
contrib = se->avg.runnable_avg_sum * scale_load_down(se->load.
weight);
contrib /= (se->avg.avg_period + 1);
se->avg.load_avg_contrib = scale_load(contrib);
}
static inline void __update_task_entity_utilization(struct sched_entity *se)
{
u32 contrib;
/* avoid overflowing a 32-bit type w/ SCHED_LOAD_SCALE */
contrib = se->avg.running_avg_sum * scale_load_down(SCHED_LOAD_
SCALE);
contrib /= (se->avg.avg_period + 1);
se->avg.utilization_avg_contrib = scale_load(contrib);
}
Back to top | Article view | linux.kernel
csiph-web