All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 3/5] nfsd: add a header describing upcall for clname tracking daemon
Date: Wed, 14 Dec 2011 16:53:22 -0500	[thread overview]
Message-ID: <20111214215322.GC7623@fieldses.org> (raw)
In-Reply-To: <1323870891-3124-4-git-send-email-jlayton@redhat.com>

On Wed, Dec 14, 2011 at 08:54:49AM -0500, Jeff Layton wrote:
> Add a new header that describes the clname tracking daemon upcall. The
> daemon takes a versioned binary struct. Hopefully this should allow us
> to revise the struct later if it becomes necessary.
> 
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
>  include/linux/nfsd/clstate.h |   59 ++++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 59 insertions(+), 0 deletions(-)
>  create mode 100644 include/linux/nfsd/clstate.h
> 
> diff --git a/include/linux/nfsd/clstate.h b/include/linux/nfsd/clstate.h
> new file mode 100644
> index 0000000..d571aa5
> --- /dev/null
> +++ b/include/linux/nfsd/clstate.h
> @@ -0,0 +1,59 @@
> +/*
> + * fs/nfsd/clstate.h - data type and function declarations for clstate mgmt
> + *
> + * Copyright (c) 2011 Red Hat, Inc.
> + * Author(s): Jeff Layton <jlayton@redhat.com>
> + *
> + *  This program is free software; you can redistribute it and/or modify
> + *  it under the terms of the GNU General Public License as published by
> + *  the Free Software Foundation; either version 2 of the License, or
> + *  (at your option) any later version.
> + *
> + *  This program is distributed in the hope that it will be useful,
> + *  but WITHOUT ANY WARRANTY; without even the implied warranty of
> + *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> + *  GNU General Public License for more details.
> + *
> + *  You should have received a copy of the GNU General Public License
> + *  along with this program; if not, write to the Free Software
> + *  Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
> + */
> +
> +#ifndef _NFSD_CLSTATE_H
> +#define _NFSD_CLSTATE_H
> +
> +/* latest upcall version available */
> +#define CLSTATE_MAX_UPCALL_VERSION 1
> +
> +/* defined by RFC3530 */
> +#define NFS4_OPAQUE_LIMIT 1024
> +
> +/*
> + * Maximum length of an address string. We could use INET6_ADDRSTRLEN, but
> + * the kernel and userspace definitions are different.
> + */
> +#define CLSTATE_MAX_ADDRESS_LEN 48
> +
> +enum clstate_command {
> +	Cl_Create,		/* create a record for this cm_id */
> +	Cl_Expire,		/* remove record for this cm_id */
> +	Cl_NrToReclaim,		/* how many client records need reclaim? */

There will probably also be other information we want from userspace on
startup, and this might be a good place to get it.  (For example, a boot
iteration and/or node id for use in clientid's.)

--b.


> +	Cl_Allow,		/* is this cm_id allowed? */
> +	Cl_GraceDone		/* grace period is complete */
> +};
> +
> +/* message struct for communication with userspace */
> +struct clstate_msg {
> +	uint8_t		cm_vers;		/* upcall version */
> +	uint8_t		cm_cmd;			/* upcall command */
> +	uint32_t	cm_xid;			/* transaction id */
> +	int16_t		cm_status;		/* return code */
> +	uint16_t	cm_len;			/* length of cm_id */
> +	unsigned char	cm_addr[CLSTATE_MAX_ADDRESS_LEN]; /* server addr */
> +	union {
> +		int64_t		cm_gracetime;	/* grace period start time */
> +		unsigned char	cm_id[NFS4_OPAQUE_LIMIT]; /* client-provided */
> +	} __attribute__((packed)) cm_u;
> +} __attribute__((packed));
> +
> +#endif /* !_NFSD_CLSTATE_H */
> -- 
> 1.7.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-12-14 21:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 13:54 [PATCH 0/5] nfsd: overhaul the client name tracking code (RFC) Jeff Layton
2011-12-14 13:54 ` [PATCH 1/5] nfsd: add nfsd4_client_tracking_ops struct and a way to set it Jeff Layton
2011-12-14 13:54 ` [PATCH 2/5] sunrpc: create nfsd dir in rpc_pipefs Jeff Layton
2011-12-14 13:54 ` [PATCH 3/5] nfsd: add a header describing upcall for clname tracking daemon Jeff Layton
2011-12-14 21:53   ` J. Bruce Fields [this message]
2011-12-15 15:14     ` Jeff Layton
2011-12-14 13:54 ` [PATCH 4/5] nfsd: add a cl_daddr field and a generic flags field to nfs4_client Jeff Layton
2011-12-14 13:54 ` [PATCH 5/5] nfsd: add the infrastructure to handle the clstate upcall Jeff Layton
2011-12-14 14:35 ` [PATCH 0/5] nfsd: overhaul the client name tracking code (RFC) Chuck Lever
2011-12-14 14:49   ` Jeff Layton
2011-12-14 20:00     ` J. Bruce Fields

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=20111214215322.GC7623@fieldses.org \
    --to=bfields@fieldses.org \
    --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 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.