mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Coddington <bcodding@redhat.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Li Lingfeng <lilingfeng3@huawei.com>,
	neilb@suse.de, okorniev@redhat.com, Dai.Ngo@oracle.com,
	tom@talpey.com, linux-nfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, yukuai1@huaweicloud.com,
	houtao1@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com,
	lilingfeng@huaweicloud.com
Subject: Re: [PATCH] nfsd: decrease cl_cb_inflight if fail to queue cb_work
Date: Fri, 21 Feb 2025 10:11:30 -0500	[thread overview]
Message-ID: <7034A7D2-7AE3-4704-B30A-7D0D477307B0@redhat.com> (raw)
In-Reply-To: <6bdec87c369b61b515a29a6d661b1e9473fba24c.camel@kernel.org>

On 21 Feb 2025, at 9:58, Jeff Layton wrote:

> On Fri, 2025-02-21 at 09:46 -0500, Benjamin Coddington wrote:
>> On 21 Feb 2025, at 9:37, Jeff Layton wrote:
>>
>>> On Fri, 2025-02-21 at 09:06 -0500, Benjamin Coddington wrote:
>>>> On 18 Feb 2025, at 9:40, Jeff Layton wrote:
>>>
>>> lease_breaking() is only checked when want_write is false. IOW, if
>>> you're breaking the lease for write, then lm_break is always called.
>>>
>>> Is that a bug or a feature? I'm not sure, but it's been that way since
>>> ~2011.
>>
>> Yeah.. why?
>>
>> Thanks I missed that detail when I refreshed my memory of it just now.
>> Seems like you'd want to avoid constantly calling lm_break for both cases,
>> spamming the lock manager adds nothing.  2 cents.
>>
>
> Sorry, it doesn't get called every time. If want_write is called then
> we _do_ check FL_UNLOCK_PENDING. IOW, you can get a downgrade attempt
> first, and then a full unlock request later.
>
> nfsd doesn't do downgrades. It recalls the object either way. So,
> ignoring subsequent lm_break calls is the right thing to do, I think.

Got it, thanks for clarifying this behavior for me!

Ben


  reply	other threads:[~2025-02-21 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 13:54 Li Lingfeng
2025-02-18 13:58 ` Jeff Layton
2025-02-18 14:29   ` Jeff Layton
2025-02-18 14:31     ` Chuck Lever
2025-02-18 14:40       ` Jeff Layton
2025-02-18 15:02         ` Chuck Lever
2025-02-18 15:51           ` Jeff Layton
2025-02-18 16:01             ` Chuck Lever
2025-02-21 14:06         ` Benjamin Coddington
2025-02-21 14:37           ` Jeff Layton
2025-02-21 14:46             ` Benjamin Coddington
2025-02-21 14:58               ` Jeff Layton
2025-02-21 15:11                 ` Benjamin Coddington [this message]
2025-02-18 14:24 ` cel

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=7034A7D2-7AE3-4704-B30A-7D0D477307B0@redhat.com \
    --to=bcodding@redhat.com \
    --cc=Dai.Ngo@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=houtao1@huawei.com \
    --cc=jlayton@kernel.org \
    --cc=lilingfeng3@huawei.com \
    --cc=lilingfeng@huaweicloud.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.com \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai1@huaweicloud.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®