[sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool
MORITA Kazutaka
morita.kazutaka at lab.ntt.co.jp
Thu Oct 25 10:08:25 CEST 2012
At Thu, 25 Oct 2012 09:14:32 +0200,
Bastian Scholz wrote:
>
> Am 2012-10-22 08:43, schrieb MORITA Kazutaka:
> > Yes, we need more numbers with various conditions to change the
> > design. (I like this patch implementation, which uses the same code
> > with ordered work queue, though.)
> >
> > I think of trying it, but I wish more users would test it too.
>
> Hi Kazutaka,
>
> If I want to test it, can I use the thread branch from git?
Yes, thanks!
So far, I've not encountered situations where my patch shows worse
performance. In most cases, queue_work is called only from one
thread, so serializing at queue_work is unlikely to be a problem.
Another contention is between queue_work and worker_routine, but
worker threads spend the most of time doing disk I/Os and it also
couldn't be a problem on my environment.
Thanks,
Kazutaka
More information about the sheepdog
mailing list