All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>,
	Jason Gunthorpe <jgg@nvidia.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v1] RDMA/core: Fix check_flush_dependency splat on addr_wq
Date: Wed, 24 Aug 2022 12:20:56 +0300	[thread overview]
Message-ID: <YwXtePKW+sn/89M6@unreal> (raw)
In-Reply-To: <584E7212-BC09-48E1-A27E-725E54FA075E@oracle.com>

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@kernel.org> 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.
Jason, what do you think?

Thanks

  reply	other threads:[~2022-08-24  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 15:30 [PATCH v1] RDMA/core: Fix check_flush_dependency splat on addr_wq Chuck Lever
2022-08-23  8:09 ` Leon Romanovsky
2022-08-23 13:58   ` Chuck Lever III
2022-08-24  9:20     ` Leon Romanovsky [this message]
2022-08-24 14:09       ` Chuck Lever III
2022-08-26 13:29         ` Jason Gunthorpe
2022-08-26 14:02           ` Chuck Lever III
2022-08-26 14:08             ` Jason Gunthorpe
2022-08-26 19:57               ` Chuck Lever III
2022-08-29 16:45                 ` Jason Gunthorpe
2022-08-29 17:14                   ` Chuck Lever III
2022-08-29 17:22                     ` Jason Gunthorpe
2022-08-29 18:15                       ` Chuck Lever III
2022-08-29 18:26                         ` Jason Gunthorpe
2022-08-29 19:31                           ` Chuck Lever III

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YwXtePKW+sn/89M6@unreal \
    --to=leon@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jgg@nvidia.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.