Method and apparatus for extending traditional operating systems file systems
First Claim
1. In a computer system having a kernel supporting an interface definition language, a file system comprising:
- an object framework, said object framework including;
a set of proxy vnodes;
a set of memcache vnodes; and
, a set of storage vnodes;
wherein both said set of proxy vnodes and said set of memcache vnodes are coupled for communication with said set of storage vnodes through the use of said interface definition language, and said set of proxy vnodes are coupled for communication with said set of memcache vnodes through the use of a set of pointers.
1 Assignment
0 Petitions
Accused Products
Abstract
In a computer system having a kernel supporting an interface definition language, a file system composed of an object framework. The object framework includes a set of proxy vnodes, a set of memcache vnodes, and a set of storage vnodes. The set of proxy vnodes and the set of memcache vnodes are linked to the set of storage vnodes through the use of the interface definition language, and the set of proxy vnodes are linked to the set of memcache vnodes through the use of a set of pointers. Each proxy vnode of said set of proxy vnodes is typed so as to differentiate between a set of file system objects such as files, directories and devices. The set of memcache vnodes forms an interface to a virtual memory system while the set of storage vnodes forms an interface to an underlying file system. The file system also uses a set of file paging interfaces that support extensions to the file system while providing full coherence of data.
82 Citations
18 Claims
-
1. In a computer system having a kernel supporting an interface definition language, a file system comprising:
-
an object framework, said object framework including;
a set of proxy vnodes;
a set of memcache vnodes; and
,a set of storage vnodes;
wherein both said set of proxy vnodes and said set of memcache vnodes are coupled for communication with said set of storage vnodes through the use of said interface definition language, and said set of proxy vnodes are coupled for communication with said set of memcache vnodes through the use of a set of pointers. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
a first layer having a first proxy vnode of said set of proxy vnodes, a first memcache vnode of said set of memcache vnodes, and a first storage vnode of said set of storage vnodes; and
,a second layer having a second proxy vnode of said set of proxy vnodes, and a second memcache vnode of said set of memcache vnodes.
-
-
15. The file system of claim 14, wherein said first layer is configured for compressing of any file data received from said second layer and decompression of any file data sent to said first layer.
-
16. The file system of claim 14, wherein said first layer coherently caches file data and acts as a pager for supplying file data to said second layer.
-
17. The file system of claim 14, wherein said second layer coherently caches file data from said first layer and acts as a pager for supplying file data to a third layer.
-
18. A method for defining a file system for a computer system having a kernel supporting an interface definition language, comprising the steps of:
-
defining an object framework including a set a proxy vnodes, a set of memcache vnodes, and a set of storage vnodes;
linking both said set of proxy vnodes and said set of memcache vnodes to said set of storage vnodes through the use of said interface definition language; and
,linking said set of proxy vnodes to said set of memcache vnodes through the use of a set of pointers.
-
Specification