From: Roland Dreier <rdreier@cisco.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: ericvh@gmail.com, linux-kernel@vger.kernel.org,
v9fs-devel@vger.kernel.org, rminnich@dancer.ca.sandia.gov,
lionkov@lanl.gov
Subject: Re: [PATCH 01/03] 9prdma: RDMA Transport Support for 9P
Date: Mon, 06 Oct 2008 15:35:51 -0700 [thread overview]
Message-ID: <adavdw5nygo.fsf@cisco.com> (raw)
In-Reply-To: <48EA549E.1050001@opengridcomputing.com> (Tom Tucker's message of "Mon, 06 Oct 2008 13:10:38 -0500")
> > Is your protocol documented anywhere? It seems npfs has support for the
> > same transport.
> When using SEND/RECV, there isn't a protocol other than 9P
> itself. Once we add RDMA ops, one will be required to exchange RKEY,
> etc... But maybe I don't understand the question?
No, that makes sense. I don't know that much about 9p but I guess it's
fairly transport agnostic, so if you're just sending/receiving standard
9p messages then there's probably nothing to exchange.
- R.
next prev parent reply other threads:[~2008-10-06 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 0:08 [PATCH 00/03] RDMA Transport Support for 9P Tom Tucker
2008-10-02 0:08 ` [PATCH 01/03] 9prdma: " Tom Tucker
2008-10-02 0:08 ` [PATCH 02/03] 9prdma: Makefile change for the RDMA transport Tom Tucker
2008-10-02 0:08 ` [PATCH 03/03] 9prdma: Kconfig changes " Tom Tucker
2008-10-02 5:11 ` [PATCH 01/03] 9prdma: RDMA Transport Support for 9P Roland Dreier
2008-10-06 18:10 ` Tom Tucker
2008-10-06 22:35 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 15:56 [PATCH 00/03] " Tom Tucker
2008-10-06 15:56 ` [PATCH 01/03] 9prdma: " Tom Tucker
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=adavdw5nygo.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lionkov@lanl.gov \
--cc=rminnich@dancer.ca.sandia.gov \
--cc=tom@opengridcomputing.com \
--cc=v9fs-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox