linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] RFC: RPC over AF_LOCAL, kernel client-side
Date: Tue, 22 Mar 2011 18:08:57 -0400	[thread overview]
Message-ID: <20110322220518.4360.51304.stgit@matisse.1015granger.net> (raw)

Just for sh*ts and giggles, I threw together a partial implementation
of RPC over AF_LOCAL sockets, and taught the kernel rpcbind client to
use it for registering in-kernel RPC services.

It's still a little rough around the edges.  Any thoughts?

---

Chuck Lever (4):
      SUNRPC: Use AF_LOCAL for rpcbind upcalls
      SUNRPC: Support for RPC over AF_LOCAL transports
      SUNRPC: Rename xs_encode_tcp_fragment_header()
      SUNRPC: Clean up use of curly braces in switch cases


 include/linux/sunrpc/msg_prot.h |    1 
 include/linux/sunrpc/xprt.h     |    3 
 net/sunrpc/clnt.c               |   25 +-
 net/sunrpc/rpcb_clnt.c          |   97 ++++++++-
 net/sunrpc/svc.c                |    2 
 net/sunrpc/xprtsock.c           |  417 ++++++++++++++++++++++++++++++++++++++-
 6 files changed, 506 insertions(+), 39 deletions(-)

-- 
Chuck Lever

             reply	other threads:[~2011-03-22 22:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 22:08 Chuck Lever [this message]
2011-03-22 22:09 ` [PATCH 1/4] SUNRPC: Clean up use of curly braces in switch cases Chuck Lever
2011-03-22 22:09 ` [PATCH 2/4] SUNRPC: Rename xs_encode_tcp_fragment_header() Chuck Lever
2011-03-22 22:09 ` [PATCH 3/4] SUNRPC: Support for RPC over AF_LOCAL transports Chuck Lever
2011-03-22 22:09 ` [PATCH 4/4] SUNRPC: Use AF_LOCAL for rpcbind upcalls Chuck Lever
2011-03-23 15:26 ` [PATCH 0/4] RFC: RPC over AF_LOCAL, kernel client-side Andy Adamson
2011-03-23 15:56   ` Chuck Lever
2011-03-23 17:02     ` Trond Myklebust

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=20110322220518.4360.51304.stgit@matisse.1015granger.net \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).