From: Neil Brown <neilb@suse.de>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: Tom Talpey <Thomas.Talpey@netapp.com>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Peter Leckie <pleckie@melbourne.sgi.com>,
Greg Banks <gnb@sgi.com>
Subject: Re: [RFC,PATCH 7/15] knfsd: create RDMA transport in nfssvc
Date: Tue, 22 May 2007 16:21:49 +1000 [thread overview]
Message-ID: <18002.35837.867422.793900@notabene.brown> (raw)
In-Reply-To: message from Tom Tucker on Monday May 21
I must sat that I am hitting acronym-overload hear.
RDMA IB iWARP OFA-API SQ-CQ SQ-WR sge max_qp_rd_atom ....
But to the topic of registering the RDMA listening point....
I now understand the point of port 2050 I think. RDMA adds to the
protocol. As well as all the bytes of the RPC request, there is
information about different ..uhm... regions (?) of the message.
This is like a scatter-gather list?
It lets you put the "write" data correctly aligned into a page,
so that we could eventually use the 'splice' technology to achieve
zero-copy write.
But we still have this concept of a different transport to handle
properly.
A bit of an aside: You mention that with "IB", IP is not used, so there
is no number. I assume you mean no IP address of the client? In that
situation, how do we identify the client for authorisation purposes?
More on-topic, we need to consider how this interacts with
/proc/fs/nfsd/portlist
This file can be written to and read from.
When writing, you write a decimal number of a file descriptor.
That fd should be a socket on which to expect incoming requests -
either a UDP socket or a TCP socket that is listening.
How can we extend that to RDMA? What sort of handle does user-space
use for talking over one of these DDP interfaces?
We could arrange that writing e.g.
RDMA TCP 2050
did what you want, but I would much rather avoid that sort of stuff.
When reading from a file you get one line per active transport:
ipv4 tcp 0.0.0.0 2049
ipv4 udp 0.0.0.0 2049
What would we read for RDMA? You say that it uses TCP. Can it use
UDP instead? Might it make sense to listen on only one interface?
Is there an IPv6 version of RDMA??
It seems like a real pity that it couldn't get shoe-horned into a
socket interface.
It would seem that the msg_control part of sendmsg/recvmsg would be
ideal for managing the details of data placement.
NeilBrown
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-05-22 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 17:45 [RFC,PATCH 7/15] knfsd: create RDMA transport in nfssvc Tom Tucker
2007-05-21 7:04 ` Neil Brown
2007-05-21 15:49 ` Tom Tucker
2007-05-22 6:21 ` Neil Brown [this message]
2007-05-22 15:59 ` Tom Tucker
2007-05-23 15:00 ` Talpey, Thomas
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=18002.35837.867422.793900@notabene.brown \
--to=neilb@suse.de \
--cc=Thomas.Talpey@netapp.com \
--cc=gnb@sgi.com \
--cc=nfs@lists.sourceforge.net \
--cc=pleckie@melbourne.sgi.com \
--cc=tom@opengridcomputing.com \
/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