Re: [question] implentation of smb-browsing: kernel space or user

[Mark H. Wood]

On 19 Jan 2002, H. Peter Anvin wrote:
> Followup to:  <[e-mail]>
> By author:    Urban Widmark <[e-mail]>
> In newsgroup: linux.dev.kernel
> > >
> > > I think that using the smb-file-system with a user-space mounter like
> > > mkautosmb has the problem of bad scalability in large networks, because it
> > > scans the whole network before you can access one share.
> >
> > You don't need to scan on every access. You could run the scanner only if
> > it was more than x minutes since the last scan. You could run the scanner
> > independently of any attempts to access autofs.
> >
>
> There is probably no need to even do that.  SMB contains a browser
> list protocol, and Samba (nmbd) can participate in it.  You should be
> able to read it out of there.

Yes.  Consider the way DNS is implemented, and do likewise.  That is,
there's a library which presents a single standard interface for mapping
names (shares, hosts, whatever) to addresses in the NMB namespace.  It
can be configured to use a local nmbd if you have one, a nearby nmbd if
you choose, LDAP searching of the local ADS forest if there is one, etc.
without reconfiguring the app.s.

It might even be grafted onto the existing resolver library, although the
name resolution API may be due for an overhaul to generalize it over a
wider variety of name resolution services.

How the results are presented to app.s is a separate question, and I
believe that there are methods of implementing filesystems almost entirely
in userspace.

-- 
Mark H. Wood, Lead System Programmer   [e-mail]
Our lives are forever changed.  But *that* is exactly as it always was.