From: "Chuck Lever" <cel@kernel.org>
To: "Prabhakar Pujeri" <prabhakar.pujeri@dell.com>,
"Jeff Layton" <jlayton@kernel.org>
Cc: NeilBrown <neil@brown.name>,
"Olga Kornievskaia" <okorniev@redhat.com>,
"Dai Ngo" <Dai.Ngo@oracle.com>, "Tom Talpey" <tom@talpey.com>,
"Donald Hunter" <donald.hunter@gmail.com>,
"Jakub Kicinski" <kuba@kernel.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] nfsd: report NFSv4 grace state through Netlink
Date: Fri, 28 Aug 2026 09:43:41 -0400 [thread overview]
Message-ID: <be88803f-4932-4b7c-8752-8a228bd67407@app.fastmail.com> (raw)
In-Reply-To: <20260828133351.923-1-prabhakar.pujeri@dell.com>
On Fri, Aug 28, 2026, at 9:33 AM, Prabhakar Pujeri wrote:
> On Thu, 2026-08-27 at 09:06 -0400, Chuck Lever wrote:
>> I'd like any new API to avoid foreclosing the ability to move exports
>> in and out of grace individually.
>
> Thanks, that makes sense. A network-namespace-wide boolean would remain
> useful as an aggregate, but the current single attribute does not make
> its scope explicit enough for future per-export grace.
>
> I will avoid freezing that ABI in this reroll. I'll drop the
> grace-reporting patch from the client-visibility v2 and post the client
> dump and state-count patches separately.
>
> I'll follow up with a dedicated grace-status proposal whose records
> carry an explicit scope, so it can represent the server-wide state today
> and individual exports later. I also prefer to get agreement on the
> export identity before adding that part speculatively.
>
> Does that direction address your concern?
WFM!
--
Chuck Lever
next prev parent reply other threads:[~2026-08-28 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 6:51 [PATCH v1 0/3] nfsd: expose NFSv4 client " Prabhakar Pujeri
2026-08-25 6:51 ` [PATCH v1 1/3] nfsd: report NFSv4 grace " Prabhakar Pujeri
2026-08-25 12:10 ` Jeff Layton
2026-08-27 4:51 ` Prabhakar Pujeri
2026-08-27 13:06 ` Chuck Lever
2026-08-28 13:33 ` Prabhakar Pujeri
2026-08-28 13:43 ` Chuck Lever [this message]
2026-08-25 6:51 ` [PATCH v1 2/3] nfsd: add a Netlink dump of NFSv4 clients Prabhakar Pujeri
2026-08-25 6:51 ` [PATCH v1 3/3] nfsd: report per-client NFSv4 state usage through Netlink Prabhakar Pujeri
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=be88803f-4932-4b7c-8752-8a228bd67407@app.fastmail.com \
--to=cel@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=donald.hunter@gmail.com \
--cc=jlayton@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=prabhakar.pujeri@dell.com \
--cc=tom@talpey.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®