From: Tom Tucker <tom@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: neilb@suse.de, nfs@lists.sourceforge.net, gnb@sgi.com
Subject: Re: [RFC,PATCH 00/10] rdma: SVCRDMA Transport Driver
Date: Mon, 22 Oct 2007 21:44:13 -0500 [thread overview]
Message-ID: <471D5FFD.8090601@opengridcomputing.com> (raw)
In-Reply-To: <20071022220219.GW583@fieldses.org>
J. Bruce Fields wrote:
> On Fri, Oct 19, 2007 at 04:53:04PM -0500, Tom Tucker wrote:
>
>> This patchset implements the RDMA Transport Driver for the
>> server transport switch. This patchset has been tested with iozone
>> and Connectathon over NFSv3.
>>
>
> Do you want these applied?
>
>
Yes. I'm assuming that this would include all incremental patches prior
to the RDMA transport driver as well?
>> This patchset along with all of the previous server side
>> transport switches are also available in this git tree:
>>
>> git://linux-nfs.org/~tomtucker/nfs-rdma-dev-2.6.git
>>
>
> This is missing a couple changes I made in my version: the two I notice
> are that I merged both "svc: Don't copy xprt_class data into svc_xprt
> instance" and "svc: Rename xpo_release to xpo_release_rqst" in with the
> previous patches.
>
>
Yes, please. Should I post my subsequent patches relative to your git
tree? That might make life easier.
> So I've ignored that for now and just applied these new patches on top
> of mine. I also rebased onto the latest linus git.
>
I should compare your tot to mine to make sure we're not out of sync.
I'll do that tomorrow.
FYI, I'm working on a "perfect hindsight" branch as well. I'll let you
know when I've got that done.
> Also, there's still that small sysctl complaint from Andrew outstanding,
> which I haven't had the time to look into.
>
>
> --b.
>
-------------------------------------------------------------------------
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/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-10-23 2:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 21:53 [RFC,PATCH 00/10] rdma: SVCRDMA Transport Driver Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 01/10] rdma: ONCRPC RDMA Header File Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 02/10] rdma: sysctl for SVCRDMA transport module Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 03/10] rdma: SVCRMDA Header File Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 04/10] rdma: SVCRDMA Transport Module Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 05/10] rdma: SVCRDMA Core Transport Services Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 06/10] rdma: SVCRDMA recvfrom Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 07/10] rdma: SVCRDMA sendto Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 08/10] rdma: ONCRPC RDMA protocol marshalling Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 09/10] rdma: makefile Tom Tucker
2007-10-19 21:56 ` [RFC,PATCH 10/10] rdma: Kconfig Tom Tucker
2007-10-22 22:02 ` [RFC,PATCH 00/10] rdma: SVCRDMA Transport Driver J. Bruce Fields
2007-10-22 22:03 ` J. Bruce Fields
2007-10-23 2:44 ` Tom Tucker [this message]
2007-10-23 18:05 ` 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=471D5FFD.8090601@opengridcomputing.com \
--to=tom@opengridcomputing.com \
--cc=bfields@fieldses.org \
--cc=gnb@sgi.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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