Re: scheduler policy question

Hubert Tonneau wrote: > > Benchmarking Pliant (http://pliant.cx/) semaphores led to unexpectedly > low results. The problem to either kernel bad features or bugs in my > program since Pliant uses no glue library such as glibc: it calls > directly kernel funtions. > > Not enough scheduling

Re: scheduler policy question

Hubert Tonneau wrote: Benchmarking Pliant (http://pliant.cx/) semaphores led to unexpectedly low results. The problem to either kernel bad features or bugs in my program since Pliant uses no glue library such as glibc: it calls directly kernel funtions. Not enough scheduling problem:

scheduler policy question

Benchmarking Pliant (http://pliant.cx/) semaphores led to unexpectedly low results. The problem to either kernel bad features or bugs in my program since Pliant uses no glue library such as glibc: it calls directly kernel funtions. Not enough scheduling problem: - I