* Con Kolivas <kernel _at_ kolivas.org> wrote: > What this one does is the following; If there is a "nice" difference > between tasks running on logical cores of the same cpu, the more > "nice" one will run a proportion of time equal to the timeslice it > would have been given relative to the less "nice" task. ie a nice 19 > task running on one core and the nice 0 task running on the other core > will let the nice 0 task run continuously (102ms is normal timeslice) > and the nice 19 task will only run for the last 10ms of time the nice > 0 task is running. This makes for a much more balanced resource > distribution, gives significant preference to the higher priority > task, but allows them to benefit from running on both logical cores. this is a really good rule conceptually - the higher prio task will get at least as much raw (unshared) physical CPU slice as it would get without HT. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [PATCH] 2.6.1 Hyperthread smart "nice" 2Con Kolivas
- [PATCH] 2.6.1 Hyperthread smart "nice"Con Kolivas
- Re: [PATCH] 2.6.1 Hyperthread smart "nice"Jos Hulzink
- [PATCH] 2.6.1 Hyperthread smart "nice" 2Con Kolivas
- Prev by Date: [2.4] heavy-load under swap space shortage
- Next by Date: Re: 2.6 input drivers FAQ (ir-kbd-gpio.ko)
- Previous by thread: [PATCH] 2.6.1 Hyperthread smart "nice" 2
- Next by thread: Re: [PATCH] 2.6.1 Hyperthread smart "nice" 2
- Indexes:[Main][Thread]