From: Chuck Lever <chuck.lever@oracle.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [RFC,PATCH 02/20] svc: xpt_detach and xpt_free
Date: Wed, 29 Aug 2007 13:05:48 -0400 [thread overview]
Message-ID: <46D5A76C.9030901@oracle.com> (raw)
In-Reply-To: <20070820162325.15224.71015.stgit@dell3.ogc.int>
[-- Attachment #1: Type: text/plain, Size: 5061 bytes --]
Hi Tom-
Tom Tucker wrote:
> Add transport switch functions to ensure that no additional receive
> ready events will be delivered by the transport (xpt_detach),
> and another to free memory associated with the transport (xpt_free).
> Change svc_delete_socket() and svc_sock_put() to use the new
> transport functions.
Can you explain why these exist as separate functions? I'm wondering if
there is an opportunity here to make the server architecture simpler
here rather than merely mimicking the existing design.
> Signed-off-by: Greg Banks <gnb@melbourne.sgi.com>
> Signed-off-by: Peter Leckie <pleckie@melbourne.sgi.com>
> Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
> ---
>
> include/linux/sunrpc/svcsock.h | 12 ++++++++++
> net/sunrpc/svcsock.c | 50 +++++++++++++++++++++++++++++++++-------
> 2 files changed, 53 insertions(+), 9 deletions(-)
>
> diff --git a/include/linux/sunrpc/svcsock.h b/include/linux/sunrpc/svcsock.h
> index 4792ed6..27c5b1f 100644
> --- a/include/linux/sunrpc/svcsock.h
> +++ b/include/linux/sunrpc/svcsock.h
> @@ -15,6 +15,18 @@ struct svc_xprt {
> const char *xpt_name;
> int (*xpt_recvfrom)(struct svc_rqst *rqstp);
> int (*xpt_sendto)(struct svc_rqst *rqstp);
> + /*
> + * Detach the svc_sock from it's socket, so that the
> + * svc_sock will not be enqueued any more. This is
> + * the first stage in the destruction of a svc_sock.
> + */
> + void (*xpt_detach)(struct svc_sock *);
> + /*
> + * Release all network-level resources held by the svc_sock,
> + * and the svc_sock itself. This is the final stage in the
> + * destruction of a svc_sock.
> + */
> + void (*xpt_free)(struct svc_sock *);
> };
I generally prefer that this kind of documentation should appear in a
separate document or a larger block comment outside the structure
definition, but that's just MO.
Also, these functions are supposed to be generic -- should they take an
svc_sock * or something more abstract?
I'm not sure I like the names "detach" and "free", but again that's just
my personal taste. The client side uses "close" and "destroy", and I
lean towards making the client and server consistent with each other.
> /*
> diff --git a/net/sunrpc/svcsock.c b/net/sunrpc/svcsock.c
> index 789d94a..4956c88 100644
> --- a/net/sunrpc/svcsock.c
> +++ b/net/sunrpc/svcsock.c
> @@ -84,6 +84,8 @@ static void svc_udp_data_ready(struct s
> static int svc_udp_recvfrom(struct svc_rqst *);
> static int svc_udp_sendto(struct svc_rqst *);
> static void svc_close_socket(struct svc_sock *svsk);
> +static void svc_sock_detach(struct svc_sock *);
> +static void svc_sock_free(struct svc_sock *);
>
> static struct svc_deferred_req *svc_deferred_dequeue(struct svc_sock *svsk);
> static int svc_deferred_recv(struct svc_rqst *rqstp);
> @@ -378,14 +380,9 @@ svc_sock_put(struct svc_sock *svsk)
> if (atomic_dec_and_test(&svsk->sk_inuse)) {
> BUG_ON(! test_bit(SK_DEAD, &svsk->sk_flags));
>
> - dprintk("svc: releasing dead socket\n");
> - if (svsk->sk_sock->file)
> - sockfd_put(svsk->sk_sock);
> - else
> - sock_release(svsk->sk_sock);
> if (svsk->sk_info_authunix != NULL)
> svcauth_unix_info_release(svsk->sk_info_authunix);
> - kfree(svsk);
> + svsk->sk_xprt->xpt_free(svsk);
> }
> }
Why wouldn't xpt_free also do the auth-info release?
> @@ -889,6 +886,8 @@ static const struct svc_xprt svc_udp_xpr
> .xpt_name = "udp",
> .xpt_recvfrom = svc_udp_recvfrom,
> .xpt_sendto = svc_udp_sendto,
> + .xpt_detach = svc_sock_detach,
> + .xpt_free = svc_sock_free,
> };
>
> static void
> @@ -1331,6 +1330,8 @@ static const struct svc_xprt svc_tcp_xpr
> .xpt_name = "tcp",
> .xpt_recvfrom = svc_tcp_recvfrom,
> .xpt_sendto = svc_tcp_sendto,
> + .xpt_detach = svc_sock_detach,
> + .xpt_free = svc_sock_free,
> };
>
> static void
> @@ -1770,6 +1771,38 @@ bummer:
> }
>
> /*
> + * Detach the svc_sock from the socket so that no
> + * more callbacks occur.
> + */
> +static void
> +svc_sock_detach(struct svc_sock *svsk)
> +{
> + struct sock *sk = svsk->sk_sk;
> +
> + dprintk("svc: svc_sock_detach(%p)\n", svsk);
> +
> + /* put back the old socket callbacks */
> + sk->sk_state_change = svsk->sk_ostate;
> + sk->sk_data_ready = svsk->sk_odata;
> + sk->sk_write_space = svsk->sk_owspace;
> +}
> +
> +/*
> + * Free the svc_sock's socket resources and the svc_sock itself.
> + */
> +static void
> +svc_sock_free(struct svc_sock *svsk)
> +{
> + dprintk("svc: svc_sock_free(%p)\n", svsk);
> +
> + if (svsk->sk_sock->file)
> + sockfd_put(svsk->sk_sock);
> + else
> + sock_release(svsk->sk_sock);
> + kfree(svsk);
> +}
> +
> +/*
> * Remove a dead socket
> */
> static void
> @@ -1783,9 +1816,8 @@ svc_delete_socket(struct svc_sock *svsk)
> serv = svsk->sk_server;
> sk = svsk->sk_sk;
>
> - sk->sk_state_change = svsk->sk_ostate;
> - sk->sk_data_ready = svsk->sk_odata;
> - sk->sk_write_space = svsk->sk_owspace;
> + if (svsk->sk_xprt->xpt_detach)
> + svsk->sk_xprt->xpt_detach(svsk);
>
> spin_lock_bh(&serv->sv_lock);
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 315 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
email;internet:chuck dot lever at nospam oracle dot com
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-29 17:06 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 16:20 [RFC,PATCH 00/20] svc: Server Side Transport Switch Tom Tucker
2007-08-20 16:23 ` [RFC, PATCH 01/20] svc: Add svc_xprt transport switch structure Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 02/20] svc: xpt_detach and xpt_free Tom Tucker
2007-08-29 17:05 ` Chuck Lever [this message]
2007-08-29 17:08 ` J. Bruce Fields
2007-08-20 16:23 ` [RFC,PATCH 03/20] svc: xpt_prep_reply_hdr Tom Tucker
2007-08-29 17:15 ` Chuck Lever
2007-08-29 18:28 ` Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 05/20] svc: xpt_max_payload Tom Tucker
2007-08-29 17:40 ` Chuck Lever
2007-08-29 19:06 ` Tom Tucker
2007-08-20 16:23 ` [RFC, PATCH 06/20] svc: export svc_sock_enqueue, svc_sock_received Tom Tucker
2007-08-21 16:03 ` Chuck Lever
2007-08-21 18:08 ` Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 07/20] svc: centralise close handling Tom Tucker
2007-08-29 18:16 ` Chuck Lever
2007-08-20 16:23 ` [RFC,PATCH 08/20] svc: centralise accept handling Tom Tucker
2007-08-29 18:40 ` Chuck Lever
2007-08-29 23:56 ` Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 09/20] svc: Add SK_LISTENER flag Tom Tucker
2007-08-29 18:41 ` Chuck Lever
2007-08-20 16:23 ` [RFC,PATCH 10/20] svc: Add generic refcount services Tom Tucker
2007-08-29 18:55 ` Chuck Lever
2007-08-29 20:19 ` Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 11/20] svc: cleanup svc_sock initialization Tom Tucker
2007-08-29 19:07 ` Chuck Lever
2007-08-20 16:23 ` [RFC,PATCH 13/20] svc: Add svc_[un]register_transport Tom Tucker
2007-08-29 19:12 ` Chuck Lever
2007-08-29 20:32 ` Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 14/20] svc: Register TCP/UDP Transports Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 15/20] svc: transport file implementation Tom Tucker
2007-08-29 19:15 ` Chuck Lever
2007-08-29 20:37 ` Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 16/20] svc: xpt_create_svc Tom Tucker
2007-08-29 19:21 ` Chuck Lever
2007-08-29 20:43 ` Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 17/20] svc: Add xpt_get_name service Tom Tucker
2007-08-20 16:23 ` [RFC,PATCH 18/20] svc: Add xpt_defer transport function Tom Tucker
2007-08-29 19:29 ` Chuck Lever
2007-08-29 21:34 ` Tom Tucker
2007-08-20 16:24 ` [RFC,PATCH 19/20] knfsd: call svc_create_svcsock Tom Tucker
2007-08-20 16:24 ` [RFC,PATCH 20/20] knfsd: create listener via portlist write Tom Tucker
2007-08-29 16:50 ` [RFC,PATCH 00/20] svc: Server Side Transport Switch Chuck Lever
2007-08-29 17:01 ` Talpey, Thomas
2007-08-29 17:59 ` Tom Tucker
2007-08-30 21:12 ` Chuck Lever
2007-08-31 1:19 ` Talpey, Thomas
2007-08-29 16:55 ` J. Bruce Fields
[not found] ` <20070820162329.15224.29032.stgit@dell3.ogc.int>
2007-08-29 17:32 ` [RFC,PATCH 04/20] svc: xpt_has_wspace Chuck Lever
2007-08-29 18:50 ` Tom Tucker
2007-08-29 17:35 ` J. Bruce Fields
2007-08-29 18:52 ` Tom Tucker
2007-08-29 18:53 ` J. Bruce Fields
2007-08-29 19:31 ` J. Bruce Fields
2007-08-29 20:11 ` Tom Tucker
2007-08-29 20:26 ` Tom Tucker
2007-08-29 20:29 ` J. Bruce Fields
2007-08-29 20:28 ` 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=46D5A76C.9030901@oracle.com \
--to=chuck.lever@oracle.com \
--cc=nfs@lists.sourceforge.net \
--cc=tom@opengridcomputing.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 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.