Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-25 Thread MORITA Kazutaka
At Thu, 25 Oct 2012 13:55:20 +0200, Bastian Scholz wrote: > Master Branch from today... > > # collie vdi create test 1G > # ./vditest test -w -B 4096 -a > > First try, some sheeps die and the vdis had failed objects. > After shutting down the remaining sheeps, restart all and > wait for recovery

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-25 Thread Bastian Scholz
OKAY... call me sheep-ripper... Am 2012-10-25 10:08, schrieb MORITA Kazutaka: 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 i

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-25 Thread MORITA Kazutaka
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 t

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-25 Thread Bastian Scholz
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

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-22 Thread MORITA Kazutaka
At Mon, 22 Oct 2012 16:46:35 +0900, MORITA Kazutaka wrote: > > At Mon, 22 Oct 2012 15:35:46 +0800, > Liu Yuan wrote: > > > > On 10/22/2012 02:50 PM, Liu Yuan wrote: > > > On 10/22/2012 02:43 PM, MORITA Kazutaka wrote: > > >> I think of trying it, but I wish more users would test it too. > > > >

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-22 Thread MORITA Kazutaka
At Mon, 22 Oct 2012 15:35:46 +0800, Liu Yuan wrote: > > On 10/22/2012 02:50 PM, Liu Yuan wrote: > > On 10/22/2012 02:43 PM, MORITA Kazutaka wrote: > >> I think of trying it, but I wish more users would test it too. > > > > I have tested it on my laptop and get the similar result. > > > > What I

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-22 Thread Liu Yuan
On 10/22/2012 02:50 PM, Liu Yuan wrote: > On 10/22/2012 02:43 PM, MORITA Kazutaka wrote: >> I think of trying it, but I wish more users would test it too. > > I have tested it on my laptop and get the similar result. > > What I am only concerned is that if pthread signal & wakeup use a signal > w

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-21 Thread Liu Yuan
On 10/22/2012 02:43 PM, MORITA Kazutaka wrote: > I think of trying it, but I wish more users would test it too. I have tested it on my laptop and get the similar result. What I am only concerned is that if pthread signal & wakeup use a signal wakeup queue instead of multi-queues, the wakeup itsel

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-21 Thread MORITA Kazutaka
At Mon, 22 Oct 2012 14:30:51 +0800, Liu Yuan wrote: > > On 10/22/2012 12:31 PM, MORITA Kazutaka wrote: > > Currently, sheep calls a pthread_create for every I/O request, but the > > overhead is not so cheap. On my environment, it takes 320 > > microseconds for sheep to process 4 KB write, but I f

Re: [sheepdog] [PATCH 0/3] work: implement a dynamically changing thread pool

2012-10-21 Thread Liu Yuan
On 10/22/2012 12:31 PM, MORITA Kazutaka wrote: > Currently, sheep calls a pthread_create for every I/O request, but the > overhead is not so cheap. On my environment, it takes 320 > microseconds for sheep to process 4 KB write, but I found that sheep > spends 30~40 microseconds in pthread_create.