From: Benny Halevy <bhalevy@panasas.com>
To: "Labiaga, Ricardo" <Ricardo.Labiaga@netapp.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, pnfs@linux-nfs.org
Subject: Re: [pnfs] [RFC 0/10] nfsd41 server backchannel for 2.6.31 (try 3)
Date: Mon, 08 Jun 2009 15:17:49 +0300 [thread overview]
Message-ID: <4A2D016D.6090205@panasas.com> (raw)
In-Reply-To: <273FE88A07F5D445824060902F7003440612BB9D-hX7t0kiaRRpT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
Merged onto the nfsd41-for-2.6.31 branch.
Thanks!
Benny
On Jun. 06, 2009, 5:48 +0300, "Labiaga, Ricardo" <Ricardo.Labiaga@netapp.com> wrote:
> Bruce, Trond,
>
> The following patch set addresses your comments on the server v4.1
> backchannel RPC functionality previously submitted. It also addresses
> Benny's comments on the implementation of the async RPC v4.1 callbacks.
> Please consider for 2.6.31.
>
> [RFC 01/11] nfsd41: Backchannel: cleanup nfs4.0 callback encode routines
> [RFC 02/11] nfsd41: Backchannel: minorversion support for the back
> channel
> [RFC 03/11] nfsd41: sunrpc: svc_tcp_recv_record()
> [RFC 04/11] nfsd41: sunrpc: Added rpc server-side backchannel handling
> [RFC 05/11] nfsd41: Backchannel: callback infrastructure
> [RFC 06/11] nfsd41: Backchannel: Add sequence arguments to callback RPC
> arguments
> [RFC 07/11] nfsd41: Backchannel: Server backchannel RPC wait queue
> [RFC 08/11] nfsd41: Backchannel: Setup sequence information
> [RFC 09/11] nfsd41: Backchannel: cb_sequence callback
> [RFC 10/11] nfsd41: Backchannel: Implement cb_recall over NFSv4.1
> [RFC 11/11] nfsd41: Refactor create_client()
>
>
> As requested, this patch set squashes the following patches recently
> submitted to the pnfs list by Alexandros, Benny, and myself.
>
> nfsd41: sunrpc: Remove unused functions
> nfsd41: sunrpc: Don't auto close the server backchannel connection
> nfsd41: sunrpc: eliminate unneeded switch statement in xs_setup_tcp()
> nfsd41: sunrpc: remove bc_close and bc_init_auto_disconnect dummy fun
> nfsd41: sunrpc: Define xprt_server_backchannel()
> nfsd41: sunrpc: create common send routine for the fore and the back
> nfsd41: sunrpc: remove bc_connect_worker()
> nfsd41: sunrpc: Document server backchannel locking
> nfsd41: sunrpc: Use free_page() to free server backchannel pages
> nfsd41: sunrpc: New svc_process_calldir()
> nfsd41: sunrpc: svc_tcp_recv_record()
> nfsd41: decode_cb_sequence does not need to actually decode ignored
> fields
>
> Thanks,
>
> - ricardo
> _______________________________________________
> pNFS mailing list
> pNFS@linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
prev parent reply other threads:[~2009-06-08 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 2:48 [RFC 0/10] nfsd41 server backchannel for 2.6.31 (try 3) Labiaga, Ricardo
[not found] ` <273FE88A07F5D445824060902F7003440612BB9D-hX7t0kiaRRpT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2009-06-06 2:49 ` [RFC 01/11] nfsd41: Backchannel: cleanup nfs4.0 callback encode routines Ricardo Labiaga
2009-06-06 2:49 ` [RFC 02/11] nfsd41: Backchannel: minorversion support for the back channel Ricardo Labiaga
2009-06-06 2:49 ` [RFC 03/11] nfsd41: sunrpc: svc_tcp_recv_record() Ricardo Labiaga
2009-06-06 2:49 ` [RFC 04/11] nfsd41: sunrpc: Added rpc server-side backchannel handling Ricardo Labiaga
2009-06-06 2:50 ` [RFC 05/11] nfsd41: Backchannel: callback infrastructure Ricardo Labiaga
2009-06-06 2:50 ` [RFC 06/11] nfsd41: Backchannel: Add sequence arguments to callback RPC arguments Ricardo Labiaga
2009-06-06 2:50 ` [RFC 07/11] nfsd41: Backchannel: Server backchannel RPC wait queue Ricardo Labiaga
2009-06-06 2:50 ` [RFC 08/11] nfsd41: Backchannel: Setup sequence information Ricardo Labiaga
2009-06-06 2:50 ` [RFC 09/11] nfsd41: Backchannel: cb_sequence callback Ricardo Labiaga
2009-06-06 2:50 ` [RFC 10/11] nfsd41: Backchannel: Implement cb_recall over NFSv4.1 Ricardo Labiaga
2009-06-06 2:50 ` [RFC 11/11] nfsd41: Refactor create_client() Ricardo Labiaga
2009-06-08 12:17 ` Benny Halevy [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=4A2D016D.6090205@panasas.com \
--to=bhalevy@panasas.com \
--cc=Ricardo.Labiaga@netapp.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.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.