From: Benny Halevy <bhalevy@panasas.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux pNFS mailing list <pnfs@linux-nfs.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC 0/10] nfsd41 backchannel patches for 2.6.32
Date: Fri, 21 Aug 2009 11:43:02 +0300 [thread overview]
Message-ID: <4A8E5E16.1090402@panasas.com> (raw)
In-Reply-To: <20090820213724.GD2451@fieldses.org>
On Aug. 21, 2009, 0:37 +0300, "J. Bruce Fields" <bfields@fieldses.org> wrote:
> On Thu, Aug 20, 2009 at 01:32:18AM +0100, Benny Halevy wrote:
>> Hi Bruce,
>>
>> Please review the following patches implementing
>> the server side nfsv4.1 backchannel.
>
> Just to make clear--you consider them ready to apply, right?
Right.
>
> (That's what I thought I understood, but the "RFC" might suggest
> otherwise.)
I sent them as "RFC" since they weren't fully reviewed yet by
the wider community, but it's not new, unbaked code.
Benny
>
> --b.
>
>> They are based on v.2.6.31-rc6 and are currently
>> queued on git://linux-nfs.org/~bhalevy/linux-pnfs.git nfsd41-all
>>
>> [PATCH RFC 01/10] nfsd41: sunrpc: svc_tcp_recv_record()
>> [PATCH RFC 02/10] nfsd41: sunrpc: Added rpc server-side backchannel handling
>> [PATCH RFC 03/10] nfsd41: sunrpc: move struct rpc_buffer def into a common header file
>> [PATCH RFC 04/10] nfsd41: Backchannel: callback infrastructure
>> [PATCH RFC 05/10] nfsd41: Backchannel: Add sequence arguments to callback RPC arguments
>> [PATCH RFC 06/10] nfsd41: Backchannel: Server backchannel RPC wait queue
>> [PATCH RFC 07/10] nfsd41: Backchannel: Setup sequence information
>> [PATCH RFC 08/10] nfsd41: Backchannel: cb_sequence callback
>> [PATCH RFC 09/10] nfsd41: Backchannel: Implement cb_recall over NFSv4.1
>> [PATCH RFC 10/10] nfsd41: Refactor create_client()
>>
>> Thanks,
>>
>> Benny
>>
prev parent reply other threads:[~2009-08-21 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 0:32 [PATCH RFC 0/10] nfsd41 backchannel patches for 2.6.32 Benny Halevy
2009-08-20 21:37 ` J. Bruce Fields
2009-08-21 8:43 ` 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=4A8E5E16.1090402@panasas.com \
--to=bhalevy@panasas.com \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@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 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).