From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2 08/10] svcrdma: Add backward direction service for RPC/RDMA transport
Date: Wed, 3 Jun 2015 15:47:41 -0400 [thread overview]
Message-ID: <20150603194741.GC9627@fieldses.org> (raw)
In-Reply-To: <4939D8DF-4AD0-477F-B06C-0E27F015BBE0@oracle.com>
On Wed, Jun 03, 2015 at 03:49:13PM -0400, Chuck Lever wrote:
>
> On Jun 2, 2015, at 11:30 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
>
> > On Mon, Jun 01, 2015 at 04:45:26PM -0400, Chuck Lever wrote:
> >>
> >> On Jun 1, 2015, at 4:26 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> >>
> >>> On Tue, May 26, 2015 at 01:49:45PM -0400, Chuck Lever wrote:
> >>>> Introduce some pre-requisite infrastructure needed for handling
> >>>> RPC/RDMA bi-direction on the client side.
> >>>>
> >>>> On NFSv4.1 mount points, the client uses this transport endpoint to
> >>>> receive backward direction calls and route replies back to the
> >>>> NFS server.
> >>>
> >>> Am I missing something, or is this pretty much dead code for now?
> >>>
> >>> In which case, I'd rather wait on it.
> >>
> >> When I submit the client-side backchannel patches, should I submit
> >> this patch through Anna and request your Acked-by?
> >
> > Sure, feel free to add my Acked-by.
> >
> > Or I guess I won't worry too much about some dead code if the
> > client-side patches are coming soon.
>
> There are more pre-requisites on the client than there are on the server.
> I anticipate it will be at least two more merge windows before the client
> will be ready to merge backchannel support.
>
> I’ll add this patch back into the client backchannel series.
OK.--b.
next prev parent reply other threads:[~2015-06-03 19:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 17:48 [PATCH v2 00/10] NFS/RDMA server patches for 4.2 Chuck Lever
2015-05-26 17:48 ` [PATCH v2 01/10] svcrdma: Fix byte-swapping in svc_rdma_sendto.c Chuck Lever
2015-06-01 18:40 ` J. Bruce Fields
2015-06-01 18:47 ` Chuck Lever
2015-05-26 17:48 ` [PATCH v2 02/10] svcrdma: Add missing access_ok() call in svc_rdma.c Chuck Lever
2015-06-01 19:31 ` J. Bruce Fields
2015-06-01 20:01 ` Chuck Lever
2015-06-02 15:28 ` J. Bruce Fields
2015-05-26 17:48 ` [PATCH v2 03/10] SUNRPC: Move EXPORT_SYMBOL for svc_process Chuck Lever
2015-05-26 17:49 ` [PATCH v2 04/10] svcrdma: Remove svc_rdma_xdr_decode_deferred_req() Chuck Lever
2015-05-26 17:49 ` [PATCH v2 05/10] svcrdma: Keep rpcrdma_msg fields in network byte-order Chuck Lever
2015-05-26 17:49 ` [PATCH v2 06/10] svcrdma: Replace GFP_KERNEL in a loop with GFP_NOFAIL Chuck Lever
2015-05-26 17:49 ` [PATCH v2 07/10] svcrdma: Add a separate "max data segs macro for svcrdma Chuck Lever
2015-05-26 17:49 ` [PATCH v2 08/10] svcrdma: Add backward direction service for RPC/RDMA transport Chuck Lever
2015-06-01 20:26 ` J. Bruce Fields
2015-06-01 20:45 ` Chuck Lever
2015-06-02 15:30 ` J. Bruce Fields
2015-06-03 19:49 ` Chuck Lever
2015-06-03 19:47 ` J. Bruce Fields [this message]
2015-05-26 17:49 ` [PATCH v2 09/10] SUNRPC: Clean up bc_send() Chuck Lever
2015-06-01 20:19 ` Chuck Lever
2015-06-01 20:24 ` J. Bruce Fields
2015-05-26 17:50 ` [PATCH v2 10/10] rpcrdma: Merge svcrdma and xprtrdma modules into one Chuck Lever
2015-06-01 20:24 ` 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=20150603194741.GC9627@fieldses.org \
--to=bfields@fieldses.org \
--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.