On 10/10/17 8:33 pm, Rick Macklem wrote:
Julian Elischer wrote:
[stuff snipped]
On 10/10/17 4:25 am, Rick Macklem wrote:
--> As such, having a fixed reasonable # of threads is probably the best
that can be done.
- The current patch has the # of threads as a sysctl with a default
Julian Elischer wrote:
[stuff snipped]
>On 10/10/17 4:25 am, Rick Macklem wrote:
>> --> As such, having a fixed reasonable # of threads is probably the best
>>that can be done.
>>- The current patch has the # of threads as a sysctl with a default
>> of 32.
>why not set it to ncpu o
On 10/10/17 4:25 am, Rick Macklem wrote:
Ian Lepore wrote:
[stuff snipped]
taskqueue(9) is an existing mechanism to enqueue functions to execute
asynch using a pool of threads, but it doesn't answer the scalability
questions. In fact it may make them har
Ian Lepore wrote:
[stuff snipped]
>taskqueue(9) is an existing mechanism to enqueue functions to execute
>asynch using a pool of threads, but it doesn't answer the scalability
>questions. In fact it may make them harder, inasmuch as I don't think
>there's
Ian Lepore wrote:
>On Fri, 2017-10-06 at 19:02 +, Rick Macklem wrote:
>> Hi,
>>
>> I have now dropped the client side of Flexible File Layout for pNFS into head
>> and I believe it is basically working.
>> Currently when talking to mirrored DS servers, it does the Write and Commit
>> RPCs to th
On Fri, 2017-10-06 at 19:02 +, Rick Macklem wrote:
> Hi,
>
> I have now dropped the client side of Flexible File Layout for pNFS into head
> and I believe it is basically working.
> Currently when talking to mirrored DS servers, it does the Write and Commit
> RPCs to the mirrors serially. This
