On Mon, 11 Sep 2000, Daniel Phillips wrote:
> > The main problem with the stackable fs is that is has two halves, one
> > filesystem-like and one VFS-like. The VFS half must know how the
> > filesystem half was called, so it can call the underlying filesystem's
> > read() method in the same way.
>
> Why does it have to call the underlying filesystem in the same way?
> Isn't it enough just to have the correct results at the top level?
Yes and no. Currently we strive to keep the two fpos (top and bottom) in
sync, it's just easier that way from a conceptual point of view. I suppose
we could simply not care about the bottom layer, but there are some
dragons in there (to quote Al) with some of the non-trivial filesystems
like cryptfs and especially gzipfs.
It's an interesting idea, though, we'll think about it. If your idea of
doing everything as a pread/pwrite is accepted (into 2.5 probably), we
might have no other choice. :-)
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
