Re: [PATCH v1] RDMA/core: Fix check_flush_dependency splat on addr_wq

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On Aug 24, 2022, at 5:20 AM, Leon Romanovsky <leon@xxxxxxxxxx> wrote:
> 
> On Tue, Aug 23, 2022 at 01:58:44PM +0000, Chuck Lever III wrote:
>> 
>> 
>>> On Aug 23, 2022, at 4:09 AM, Leon Romanovsky <leon@xxxxxxxxxx> wrote:
>>> 
>>> On Mon, Aug 22, 2022 at 11:30:20AM -0400, Chuck Lever wrote:
> 
> <...>
> 
>>>> The xprtiod work queue is WQ_MEM_RECLAIM, so any work queue that
>>>> one of its work items tries to cancel has to be WQ_MEM_RECLAIM to
>>>> prevent a priority inversion.
>>> 
>>> But why do you have WQ_MEM_RECLAIM in xprtiod?
>> 
>> Because RPC is under a filesystem (NFS). Therefore it has to handle
>> writeback demanded by direct reclaim. All of the storage ULPs have
>> this constraint, in fact.
> 
> I don't know, this ib_addr workqueue is used when connection is created.

Reconnection is exactly when we need to ensure that creating
a new connection won't trigger more memory allocation, because
that will immediately deadlock.

Again, all network storage ULPs have this constraint.


> Jason, what do you think?
> 
> Thanks

--
Chuck Lever







[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux