Go for it mpi.. move forward.
ok beck@
On Mon, Feb 6, 2017 at 7:48 AM, Martin Pieuchot wrote:
> On 24/01/17(Tue) 13:35, Martin Pieuchot wrote:
> > Userland threads are preempt()'d when hogging a CPU or when processing
> > an AST. Currently when such a thread is preempted the scheduler looks
>
On 24/01/17(Tue) 13:35, Martin Pieuchot wrote:
> Userland threads are preempt()'d when hogging a CPU or when processing
> an AST. Currently when such a thread is preempted the scheduler looks
> for an idle CPU and puts it on its run queue. That means the number of
> involuntary context switch oft
Hi,
i did my usual tests.
current:
req/s: 3898.20
variance: 0.84
current+diff:
req/s: 3928.80
variance: 0.45
With this diff the messurements have been much more stable. The
variance of the req/s
messurements is now a lot smaller. Also the performance has increased.
For the bandwidth/s case thi
Userland threads are preempt()'d when hogging a CPU or when processing
an AST. Currently when such a thread is preempted the scheduler looks
for an idle CPU and puts it on its run queue. That means the number of
involuntary context switch often result in a migration.
This is not a problem per s
