Messages in this thread | | | Date | Thu, 01 Jun 2006 11:44:26 +0400 | From | Kirill Korotaev <> | Subject | Re: [RFC 3/5] sched: Add CPU rate hard caps |
| |
>>>> Using a timer for releasing tasks from their sinbin sounds like a bit >>>> of an overhead. Given that there could be 10s of thousands of tasks. >>> >>> >>> >>> The more runnable tasks there are the less likely it is that any of >>> them is exceeding its hard cap due to normal competition for the >>> CPUs. So I think that it's unlikely that there will ever be a very >>> large number of tasks in the sinbin at the same time. >> >> for containers this can be untrue... > > > Why will this be untrue for containers? if one container having 100 running tasks inside exceeded it's credit, it should be delayed. i.e. 100 tasks should be placed in sinbin if I understand your algo correctly. the second container having 100 tasks as well will do the same.
Kirill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |