[9fans] sanity check

["Steve Simon" <steve@quintile.net>]

Hi,

Playing with adding DFS support to my cifs client as and when
I get time.

DFS allows any path on a Windows server to be redirected to another
path on a different machine (and in theroy it could use another
protocol - CIFS, NFS, and NCP [netware] are defined).

To allow this dynamic remapping of namespace and optionally starting
a new client I plan to implement DFS as a layer [program] above cifs.

For efficency this translation should probably be done with a "clever"
algorithm (probably hash tables) and it occurs to me that I am about
to re-invent what the kernel already does.

Is it reasonable to do this mapping with a bind(2) call and let the
kernel take care of it. It might mean performing 10-50 extra binds,
is this an unresaonable load or a good use of kernel facilities?

Note: In my enviroment at least, I start cifs in my termrc behind rio
as much of my dialy work requires access to our windows servers. This
means an extended bind table will be in the namespace of everything
I use and so, if it slows things down, it will slow everything down.

-Steve