From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v5 0/9] nfsdcld: add a daemon to track NFSv4 client names on stable storage
Date: Thu, 26 Apr 2012 13:38:06 -0400 [thread overview]
Message-ID: <4F9987FE.3040605@RedHat.com> (raw)
In-Reply-To: <1328111096-28430-1-git-send-email-jlayton@redhat.com>
On 02/01/2012 10:44 AM, Jeff Layton wrote:
> This patchset is the userspace portion of the knfsd client name tracking
> overhaul. See this patch series for an explanation:
>
> nfsd: overhaul the client name tracking code
>
> This version scales back some of the changes in the last set. Since
> then, it's become clear that I'm not entirely certain what changes we'll
> need in order to handle this in a clustered configuration. Instead of
> trying to anticipate those changes, I've decided just to focus on the
> single-server case and leave any other changes for later once it becomes
> more clear what (if anything) is needed.
>
> The main changes from the last set are:
>
> - the "remove" upcall has been readded
>
> - the "init" upcall has been removed
>
> - the "check" and "update" upcalls no longer return a client index
> to the kernel
>
> - the pipe open and reopen code has been overhauled and consolidated.
> Instead of looping indefinitely when trying to reopen the file, it will
> abort the daemon if the open fails with anything besides ENOENT. If
> the pipe isn't present when the daemon starts, it now uses the inotify
> event callback to handle the opening.
>
> Jeff Layton (9):
> nfsdcld: add client tracking daemon stub
> nfsdcld: add autoconf goop for sqlite
> nfsdcld: add routines for a sqlite backend database
> nfsdcld: add remove functionality
> nfsdcld: add check/update functionality
> nfsdcld: add function to remove unreclaimed client records
> nfsdcld: make it watch for inotify events in the containing directory
> nfsdcld: add a manpage for nfsdcld
> nfsdcld: update the README
Committed.... My apologies for taking so long...
steved.
prev parent reply other threads:[~2012-04-26 18:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 15:44 [PATCH v5 0/9] nfsdcld: add a daemon to track NFSv4 client names on stable storage Jeff Layton
2012-02-01 15:44 ` [PATCH v5 1/9] nfsdcld: add client tracking daemon stub Jeff Layton
2012-04-16 14:06 ` Steve Dickson
2012-04-16 14:23 ` Jeff Layton
2012-04-16 15:14 ` Steve Dickson
2012-04-16 15:42 ` Jeff Layton
2012-04-16 16:44 ` Steve Dickson
2012-02-01 15:44 ` [PATCH v5 2/9] nfsdcld: add autoconf goop for sqlite Jeff Layton
2012-02-01 15:44 ` [PATCH v5 3/9] nfsdcld: add routines for a sqlite backend database Jeff Layton
2012-02-01 15:44 ` [PATCH v5 4/9] nfsdcld: add remove functionality Jeff Layton
2012-02-01 15:44 ` [PATCH v5 5/9] nfsdcld: add check/update functionality Jeff Layton
2012-02-01 15:44 ` [PATCH v5 6/9] nfsdcld: add function to remove unreclaimed client records Jeff Layton
2012-02-01 15:44 ` [PATCH v5 7/9] nfsdcld: make it watch for inotify events in the containing directory Jeff Layton
2012-02-01 15:44 ` [PATCH v5 8/9] nfsdcld: add a manpage for nfsdcld Jeff Layton
2012-02-01 15:44 ` [PATCH v5 9/9] nfsdcld: update the README Jeff Layton
2012-04-26 17:38 ` Steve Dickson [this message]
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=4F9987FE.3040605@RedHat.com \
--to=steved@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).