Samba performance issues: stat calls

Michael B.Allen mba2000 at
Sat Apr 5 04:07:58 GMT 2003

On Fri, 4 Apr 2003 09:53:55 -0800 (PST)
Richard Sharpe <rsharpe at> wrote:

> > > > That looks like an average of more than one stat call per SMB. Not good!
> > > 
> > > Don't you have to stat each label in a path as you walk it?
> > 
> > Yes, given how Samba works, one stat per smb is actually pretty low...
> Well, stat just hit number 1 problem for me :-)

The best solution would be to create a kernel module, extension,
whatever for each OS. For Linux this would mean just overloading the
inode_operations lookup function. I think. I have been struggling with
the kernel code. The part I don't get is I don't think I want to create
new inodes like your run-of-the-mill VFS module but rather intercept
calls into another VFS module somewhere. I started out just finding
the file_system_type, getting the superblock and returning that from
read_super. It suffices to say it didn't work. Good thing I did this
under User Mode Linux :) I have a lot of studying to do.


A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived. 

More information about the samba-technical mailing list