mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Talpey <tom@talpey.com>
To: Olga Kornievskaia <aglo@umich.edu>, Jeff Layton <jlayton@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, Neil Brown <neilb@suse.de>,
	Dai Ngo <Dai.Ngo@oracle.com>,
	Olga Kornievskaia <okorniev@redhat.com>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] nfsd: allow for up to 32 callback session slots
Date: Sun, 10 Nov 2024 22:18:33 -0500	[thread overview]
Message-ID: <c60e636f-8d69-4ec5-84d7-58cf72bbd0e8@talpey.com> (raw)
In-Reply-To: <CAN-5tyFmEUyZS-hXURdhhETwC-0MPPz0Vnu6oRW6dbZdWanpjA@mail.gmail.com>

On 11/10/2024 9:24 PM, Olga Kornievskaia wrote:
> On Sat, Nov 9, 2024 at 4:10 PM Jeff Layton <jlayton@kernel.org> wrote:
>> Sounds like a client-side capacity issue? nfs4_callback_recall()
>> returns NFS4ERR_DELAY when nfs_delegation_find_inode() returns -EAGAIN.
>> Maybe there is something weird going on there? Eventually the server
>> has no choice but to revoke an unreturned delegation.
> 
> I'm not trying to imply in any matter that there is a problem with
> either server or client side. I'm simply trying to state that there
> was a theory that having multiple cb_table slots would help in the
> case of having a lot of recalled/revoked state.  What I'm finding is
> that it doesn't seem so (and possibly makes things just slightly
> slower. But no measures were taken so my focus is elsewhere).

We should definitely understand this! I'd say that supporting multiple 
slots is worthwhile and should be merged if stable.

But if they're no better performance-wise, we're missing something. 
There's got to be something else serializing them.

Tom.

  reply	other threads:[~2024-11-11  3:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  0:31 Jeff Layton
2024-11-06 15:40 ` Chuck Lever
2024-11-06 16:44 ` Olga Kornievskaia
2024-11-06 17:12   ` Jeff Layton
2024-11-09 19:24   ` Olga Kornievskaia
2024-11-09 21:10     ` Jeff Layton
2024-11-11  2:24       ` Olga Kornievskaia
2024-11-11  3:18         ` Tom Talpey [this message]
2024-11-11 21:56   ` Olga Kornievskaia
2024-11-11 22:26     ` Jeff Layton
2024-11-11 23:32       ` Olga Kornievskaia
2024-11-09 18:50 ` Olga Kornievskaia
2024-11-09 19:26   ` Jeff Layton
2024-11-11  2:19     ` Olga Kornievskaia
2024-11-11 13:22       ` Jeff Layton
2024-11-11 14:55         ` Chuck Lever
2024-11-11 17:17           ` Olga Kornievskaia
2024-11-11 17:40             ` Jeff Layton
2024-11-11 17:56               ` Olga Kornievskaia
2024-11-11 18:17                 ` Jeff Layton
2024-11-11 18:27                   ` Jeff Layton
2024-11-11 18:46                     ` Chuck Lever
2024-11-11 18:55                     ` Olga Kornievskaia
2024-11-11 19:02                       ` Jeff Layton
2024-11-12 23:23                 ` NeilBrown
2024-11-13  0:07 ` NeilBrown
2024-11-13  1:03   ` Jeff Layton
2024-11-13  1:31     ` NeilBrown
2024-11-13 15:15       ` Jeff Layton
2024-11-14  3:19         ` NeilBrown
2024-11-14 14:19           ` 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=c60e636f-8d69-4ec5-84d7-58cf72bbd0e8@talpey.com \
    --to=tom@talpey.com \
    --cc=Dai.Ngo@oracle.com \
    --cc=aglo@umich.edu \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=okorniev@redhat.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®