Hi,

Core part of the translation system has been implemented. It 
is available for linux kernel 2.4.0-test9. It isn't usable yet, 
because only one example translator for the raw view has been 
implemented. The translation filesystem will be usable when 
more translators are available.

For more information on the translation filesystem, please
visit http://trfs.sourceforge.net/

I have attached the introduction page on this website below.

Regards.
-- 
Amit Kale
Veritas Software
(http://www.veritas.com)


The Translation Filesystem:
--------------------------
Unix filesystem interface includes a limited set of file 
operations. It is a bridge between applications and
filesystems. It enables applications to use filesystems
to store byte streams in files and create directories
to organize files in a hierarchy. The filesystem interface
is not extendible. A filesystem or any other kernel component
cannot provide functions not included in the interface. 
Bypassing the filesystem interface to create another interface
results into compatibility and maintainance problems, because
the interface cannot be supported by applications without
explicitely programming for it. The translation filesystem
enables filesystems and other kernel components to extend
the filesystem interface in a way that is compatible with
the filesystem interface. It is a framework for allowing
programs to access extentions created by filesystems or other
kernel components through the filesystem interface. 

Filesystem interface extensions created using the translation
filesystem are expressed in terms of the filesystem interface
itself. Application programs, libraries and application
developement frameworks are based on the filesystem interface.
Hence using the translation filesystem requires minimal or no
changes in application programs. Suppose a feature is to be
added to a filesystem, where the feature cannot be accessed
by calling operations in the filesystem interface. The filesystem
can allow applications to bypass the filesystem interface and
access the feature. This approach will make it necessary for
applications to use the special program interface offered by
the filesystem. Hence the interface will not be backward compatible
with existing applications. To get around the compatibility
problem, the filesystem can allow applications to use the feature
by accessing special virtual files in the filesystem. This approach
maintains backward compatibility, though it does not enable
applications to explicitly depend on the feature because it will
not be available in other filesystems. The translation filesystem
allows creation of filesystems extensions that are backward
compatible and easily adoptable and automatically available
even for filesystem that do not supporting them. 

The translation filesystem enables filesystems and kernel
components to extend the filesystem interface by allowing
them to create views for directories or files. A view is
an interface to operations not contained in the filesystem 
interface. A view contains operations in the filesystem
interface only, though their semantics may be different.
Consider an example of a tar file. A filesystem presents
a tar file as a stream of bytes. The filesystem interface
can be used to read bytes from or write bytes to the tar file.
Files contained in the tar file cannot be accessed without
interpreting the format of the tar file. A view contents 
for the tar file provides a hierarchical representation
of the tar file. The view would be a hierarchy of directories
and files contained in the tar file. Read operation on a file
contained in the view will result into a filesystem read
operation on the tar file in the area where the file is stored.
Another example of a view is raw view, which allows unbuffered
access to block devices and regular files. A filesystem interface
to a block device or a regular file provides read and write
operations which cause data to be read or written through
buffers. Use of buffers results into buffer allocation and
data copy overheads. The raw view provides unbuffered access
to a block device or a regular file allowing fast read or
write operations. 

Translation filesystem views are implemented by kernel
components called translators. The translation filesystem
manages creation and deletion of and access to views. It gives
control to a translator when a view is accessed. Expressing
an additional interface using the filesystem interface and deciding
semantics of file operations are done entirely by a translator.
A filesystem kernel component may provide views for files
managed by it by including translators specific to it in it.
Independent translators that handle views for any files can
also be implemented. Thus a filesystem can support a feature by
creating a view that is supported by two translators:
a translator that handles files in the filesystem and
a translator that handles any files. Application
programs that have an explicit dependency on the feature
can work with all filesystems.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]

Reply via email to