[OpenAFS-devel] Progress on Linux in-kernel RxRPC library

[Jeffrey Hutzelman]

On Monday, March 21, 2005 12:20:30 AM -0500 Kyle Moffett 
<mrmacman_g4@mac.com> wrote:

> Changing topics:
>

> At the moment I'm creating a userspace interface so an RxRPC call using
> the  kernel routines is something like this.  The design is still
> incomplete, so  I'm not sure about the exact appropriate usage of the
> sendmsg/recvmsg/readv/writev calls or the proper method to pack the data
> and ancillary info in the msghdr.  I am interested in your feedback and
> if  you think this is a viable method to interface RxRPC from userspace
> to kernelspace.

I read this message all of 10 minutes ago, so I haven't had a chance to 
look at it in much detail.  It looks like you're basically on the right 
track, though.  I have to think a bit about what metadata needs to be 
exposed; the fileserver, in particular, does a lot of tracking of 
connections and peers.

I'm not sure whether every security mechanism will be able to deal with the 
server having to pass in a fixed blob at startup -- the current rxkad API 
involves the server passing in a callback, but it generally doesn't 
actually do much work (it looks up a key in a file, normally).

> /*
>   * This is a server.  A single RxRPC socket in listen() mode maps to an
> arbitrary
>   * number of connections in the kernel.
>   */

This is definitely the right model.


-- Jeff