The scheduler test should test scheduler, not resource limits.
For instance, prio_num * QUEUES_PER_PRIO * 4. In case if prio_num = 16,
it's easily exits the queues maximum number allowed,
16 * 16 * 4 = 1024, plus queues created for other purposes, it can be
close to ODP_CONFIG_QUEUES. The same for
sent patch with corrected tag
On 22.01.16 12:24, Ivan Khoronzhuk wrote:
The scheduler test should test scheduler, not resource limits.
For instance, prio_num * QUEUES_PER_PRIO * 4. In case if prio_num = 16,
it's easily exits the queues maximum number allowed,
16 * 16 * 4 = 1024, plus queues
The scheduler test should test scheduler, not resource limits.
For instance, prio_num * QUEUES_PER_PRIO * 4. In case if prio_num = 16,
it's easily exits the queues maximum number allowed,
16 * 16 * 4 = 1024, plus queues created for other purposes, it can be
close to ODP_CONFIG_QUEUES. The same for
