From: dai.ngo@oracle.com
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: chuck.lever@oracle.com, jlayton@redhat.com,
viro@zeniv.linux.org.uk, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC v25 0/7] NFSD: Initial implementation of NFSv4 Courteous Server
Date: Mon, 2 May 2022 18:38:03 -0700 [thread overview]
Message-ID: <9b394762-660b-4742-b54a-2b385485b412@oracle.com> (raw)
In-Reply-To: <20220503012132.GL30550@fieldses.org>
On 5/2/22 6:21 PM, J. Bruce Fields wrote:
> On Mon, May 02, 2022 at 09:12:52PM -0400, J. Bruce Fields wrote:
>> Looks good to me.
> And the only new test failures are due to the new DELAYs on OPEN.
> Somebody'll need to fix up pynfs. (I'm not volunteering for now.)
I will fix it, since I broke it :-)
-Dai
>
> --b.
next prev parent reply other threads:[~2022-05-03 1:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 21:19 [PATCH RFC v25 0/7] NFSD: Initial implementation of NFSv4 Courteous Server Dai Ngo
2022-05-02 21:19 ` [PATCH RFC v25 1/7] NFSD: add courteous server support for thread with only delegation Dai Ngo
2022-05-02 21:19 ` [PATCH RFC v25 2/7] NFSD: add support for share reservation conflict to courteous server Dai Ngo
2022-05-02 21:19 ` [PATCH RFC v25 3/7] NFSD: move create/destroy of laundry_wq to init_nfsd and exit_nfsd Dai Ngo
2022-05-02 21:19 ` [PATCH RFC v25 4/7] fs/lock: add helper locks_owner_has_blockers to check for blockers Dai Ngo
2022-05-09 17:05 ` Jeff Layton
2022-05-02 21:19 ` [PATCH RFC v25 5/7] fs/lock: add 2 callbacks to lock_manager_operations to resolve conflict Dai Ngo
2022-05-09 15:41 ` Chuck Lever III
2022-05-09 17:03 ` Jeff Layton
2022-05-02 21:19 ` [PATCH RFC v25 6/7] NFSD: add support for lock conflict to courteous server Dai Ngo
2022-05-02 21:19 ` [PATCH RFC v25 7/7] NFSD: Show state of courtesy client in client info Dai Ngo
2022-05-03 1:12 ` [PATCH RFC v25 0/7] NFSD: Initial implementation of NFSv4 Courteous Server J. Bruce Fields
2022-05-03 1:21 ` J. Bruce Fields
2022-05-03 1:38 ` dai.ngo [this message]
2022-05-23 15:40 ` J. Bruce Fields
2022-05-23 16:57 ` dai.ngo
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=9b394762-660b-4742-b54a-2b385485b412@oracle.com \
--to=dai.ngo@oracle.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.