Re: [RFC,PATCH 15/20] svc: transport file implementation

[Tom Tucker <tom@opengridcomputing.com>]

On Wed, 2007-08-29 at 15:15 -0400, Chuck Lever wrote:
> Tom Tucker wrote:
> > Create a proc/sys/sunrpc/transport file that contains information 
> > about the currently registered transports.
> 
> How is this different than /proc/fs/nfsd/portlist ?  What does 
> user-space do with the transport name and max payload information?

The transport file contains registered transports. The portlist file
contains transports for which a listening endpoint has been created in
knfsd. The idea was that a user-mode program
(e.g. /etc/init.d/nfsserver) would scan /proc/sys/sunrpc/transport and
then write the transport string name and port to
the /proc/fs/nfsd/portlist file. 

So the transport file insulates user-mode configuration code from
changing when new transports are added, and the /proc/fs/nfsd/portlist
file insulates knfsd from changing when new transports are added.

The max payload is purely informational.

Dunno if this is the best way, but it's what I came up with...



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs