Re: VFS mediator?

[Jesse Pollard]

Pavel Machek <[e-mail]>:
> Hi!
> 
> >      > Okay, take userland nfs-server. (This thread was about userland
> >      > filesystems).
> > 
> > Yech... Nobody should be seriously considering using unfsd: it does
> > not even manage to follow the NFS protocol. That inability was one of
> > the many reasons why Olaf Kirch abandoned further develpement of unfsd
> > and started work on knfsd.
> > 
> >      > Then, make memory full of dirty pages. Imagine that nfs-server
> >      > is swapped-out by some bad luck. What you have is extremely
> >      > nasty deadlock, AFAICS. [To free memory you have to write out
> >      > dirty data, but you can't do that because you don't have enough
> >      > memory for nfs-server].
> > 
> > So that is another argument for using knfsd rather than unfsd. I will
> > agree with you that NFS is not perfect, but please judge it on its
> > actual merits and not on some trumped up charge...
> 
> Sorry, this thread was about userland filesystems, and NFS is just not
> usefull there (for read/write case).

Assuming, of course, that the daemon doesn't mprotect itself...

A user mode file system is really only good at debugging a design.

All file migration style filesystems, and user mode filesystems, have this
same problem on paging based systems:

Can't write buffer until file is migrated (file system full),
Can't migrate file until buffer memory is freed....
system hung...

Although it is usually possible to detect this deadlock and abort some
process, freeing memory (and sometimes disk space at the same time).

Swapping systems can have the equivalent problem if swap space is
oversubscribed.

The problem boils down to the same solution - don't oversubscribe memory...

I know this is a bit of a troll, but memory controls are necessary to
detect, avoid, or repair the situation.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [e-mail]

Any opinions expressed are solely my own.