<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
> Hello,<br>
><br>
> Let's assume that we have a resource which contains several volumes.<br>
> When an on-line verification is launched, all volumes are verified<br>
> together, but it seems that the job is made by only one thread.<br>
> The bottleneck in the on-line verification are not the disks, but the<br>
> CPU, as it must deal with many (for example) crc32c operations.<br>
><br>
> So my question is, could we think about an implementation which would<br>
> start one verification thread for each volume ?<br>
> It would dramatically speed-up on-line verification (for my own case,<br>
> with 4 volumes in 1 resource, it would decrease verification time from<br>
> 56 hours to 14 hours).<br>
<br>
</div></div>iirc, when we implemented it, the kernel crypto api was supposed<br>
to get asynchronous hash support "soon", so we did not bother to add our<br>
own threading/async layer over this.<br>
<br>
Guess that "soon" is very relative.<br>
<br>
Yes, we can add that as feature request<br>
somewhere on our (not so short) todo list.<br></blockquote><div><br></div><div>Lars,<br></div><div>Thank you very much for your explanation and for taking this request into account !<br></div><div>Best regards,<br>Ben<br>
<br></div></div></div></div>