[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH 2/2] block: Avoid deadlocks with bio allocation by stacking drivers
- From: Muthu Kumar <muthu lkml gmail com>
- To: Tejun Heo <tj kernel org>
- Cc: axboe kernel dk, Kent Overstreet <koverstreet google com>, david fromorbit com, dm-devel redhat com, linux-kernel vger kernel org, linux-bcache vger kernel org, Mikulas Patocka <mpatocka redhat com>, bharrosh panasas com, Vivek Goyal <vgoyal redhat com>
- Subject: Re: [dm-devel] [PATCH 2/2] block: Avoid deadlocks with bio allocation by stacking drivers
- Date: Tue, 11 Sep 2012 11:58:05 -0700
On Tue, Sep 11, 2012 at 11:45 AM, Tejun Heo <tj kernel org> wrote:
> Hello,
>
> On Tue, Sep 11, 2012 at 11:36:28AM -0700, Muthu Kumar wrote:
>> Does this preserve the CPU from which the bio was submitted
>> originally. Not familiar with cmwq, may be Tejun can clarify.
>>
>> Tejun - the question is, do we honor the rq_affinity with the above
>> rescue worker implementation?
>
> The work item would run from the same CPU but there isn't any
> mechanism to keep track of the issuing CPU if there are multiple bios
> to be rescued. Isn't rq_affinity an optimization hint? If so, I
> don't think it matters here.
>
Thanks... Just worried about performance impact.
Kent - Anything to validate that the performance is not impacted would
be really good. Otherwise, the patch looks great.
Feel free to add:
Reviewed-by: Muthukumar Ratty <muthur gmail com>
Regards,
Muthu
> Thanks.
>
> --
> tejun
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]