Hi Quinn ,
On Mon, Jan 04, 2016 at 06:27:58PM +, Quinn Tran wrote:
> >in kernel/workqueue.c to be used beyond qla2xxx, or:
>
> QT> For every work element, the pool->lock is grabbed. Unless the lock
> can be grab 1 time and the rest of the work elements piggy back on it then
> it?s worth it t
On 12/20/15, 11:13 PM, "target-devel-ow...@vger.kernel.org on behalf of
Nicholas A. Bellinger" wrote:
>On Thu, 2015-12-17 at 14:57 -0500, Himanshu Madhani wrote:
>> From: Quinn Tran
>>
>> At high traffic, the work queue can become a bottle neck.
>> Instead of putting each command on the wor
On Thu, 2015-12-17 at 14:57 -0500, Himanshu Madhani wrote:
> From: Quinn Tran
>
> At high traffic, the work queue can become a bottle neck.
> Instead of putting each command on the work queue as 1 work
> element, the fix would daisy chain a list of commands that came
> from FW/interrupt under 1 w
From: Quinn Tran
At high traffic, the work queue can become a bottle neck.
Instead of putting each command on the work queue as 1 work
element, the fix would daisy chain a list of commands that came
from FW/interrupt under 1 work element to reduce lock contention.
Signed-off-by: Quinn Tran
Sign
4 matches
Mail list logo
