From: Olaf Kirch <olaf.kirch@oracle.com>
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Cc: nfs@lists.sourceforge.net, Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: cel's patches under development
Date: Wed, 11 Apr 2007 14:02:49 +0200 [thread overview]
Message-ID: <200704111402.50435.olaf.kirch@oracle.com> (raw)
In-Reply-To: <EXNANE01OF9vJZTuG5w00000863@exnane01.hq.netapp.com>
On Wednesday 11 April 2007 13:39, Talpey, Thomas wrote:
> FWIW, I'm still looking at this from the RDMA perspective. I like the
> abstraction of the data representation, but I don't like the protocol
> specific switch statements that are in the data movement. These
Right now, the proposed rpc_data thing has two function pointers,
so no switch needed.
> are cumbersome and don't lend themselves to dynamic loading. Also,
> RDMA isn't a new protocol family, so it doesn't lend itself to an
> IPv4/IPv6 and UDP/TCP kind of switch.
How is it integrated on the client side? Wouldn't this be another
transport in terms of Chuck's transport switch? If so, it would just
provide a function for creating an RDMA specific rpc_data object
that does the right thing.
> The RDMA code turns out to not need this, because the xdr iov's
> have a clear encoding for pagelists (head->pages[]->tail).
But that means yet another non-obvious user of xdr_buf that makes
it even harder to rewrite that whole code :-) Wouldn't it be better
to make it explicit "here is a bunch of pages that I want you to
put the bulk data into"?
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@lst.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-11 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 23:09 cel's patches under development Chuck Lever
2007-04-10 15:22 ` Olaf Kirch
2007-04-10 19:32 ` Trond Myklebust
2007-04-11 6:41 ` Olaf Kirch
2007-04-11 11:39 ` Talpey, Thomas
2007-04-11 12:02 ` Olaf Kirch [this message]
2007-04-11 12:32 ` 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=200704111402.50435.olaf.kirch@oracle.com \
--to=olaf.kirch@oracle.com \
--cc=Thomas.Talpey@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.