From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: chris.mason@oracle.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Create shared API to access on-disk NSM data
Date: Tue, 12 Jan 2010 07:25:33 -0500 [thread overview]
Message-ID: <4B4C6A3D.8070009@RedHat.com> (raw)
In-Reply-To: <20100108180144.452.14970.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
On 01/08/2010 01:13 PM, Chuck Lever wrote:
> The goal of these patches is to replace duplicate code in statd and
> sm-notify that accesses the local NSM state number and the on-disk
> monitor and notify lists. This change allows us to fix bugs and add
> IPv6 support in one place instead of two.
>
> There should be little behavioral change, since the new code in
> libnsm.a is by and large copied from existing code in statd and
> sm-notify. Some error checking is enhanced. The sync(2) system call
> done after an NSM state number update is removed, since the update is
> already performed with POSIX file system calls that are all
> synchronous with permanent storage.
>
> ---
>
> Chuck Lever (3):
> statd: Use the new nsm_ file.c calls in rpc.statd
> statd: Use the new nsm_ file.c calls in sm_notify
> libnsm.a: Introduce common routines to handle persistent storage
Committed...
steved.
prev parent reply other threads:[~2010-01-12 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 18:13 [PATCH 0/3] Create shared API to access on-disk NSM data Chuck Lever
[not found] ` <20100108180144.452.14970.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-08 18:13 ` [PATCH 1/3] libnsm.a: Introduce common routines to handle persistent storage Chuck Lever
2010-01-08 18:13 ` [PATCH 2/3] statd: Use the new nsm_ file.c calls in sm_notify Chuck Lever
2010-01-08 18:13 ` [PATCH 3/3] statd: Use the new nsm_ file.c calls in rpc.statd Chuck Lever
2010-01-12 12:25 ` 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=4B4C6A3D.8070009@RedHat.com \
--to=steved@redhat.com \
--cc=chris.mason@oracle.com \
--cc=chuck.lever@oracle.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 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.