Changes between Version 13 and Version 14 of FSDesign
- Timestamp:
- 2009-10-24T11:10:58Z (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FSDesign
v13 v14 42 42 The frontend is responsible for accepting requests from the client tasks. For each client, 43 43 VFS spawns a dedicated connection fibril which handles to connection. Arguments of the incoming 44 requests are either absolute file paths, file handles of already 45 opened files, and in some special cases also VFS triplets (see below). 44 requests are either absolute file paths, file handles of already opened files, and in some special 45 cases also VFS triplets (see below). Regardless of their type, the arguments typically 46 reference some file and, as we will see later, the frontend always converts this reference to 47 an internal representation called VFS node. 46 48 47 49 ==== Paths as Arguments ==== … … 98 100 ==== Handles as Arguments ==== 99 101 100 The VFS server understands file handles and can accept them as arguments for VFS requests made by the client. Each client is using its private set of file handles to refer to its open files. VFS maintains each client's open files in a table of open files, which is local to the servicing connection fibril. The table is composed of ''vfs_file_t'' instances and the file handles index it. The associated connection fibril does not need to synchronize accesses to the table of open files because it is its exclusive owner. 102 The VFS server understands file handles and can accept them as arguments for VFS requests made by the client. Each client is using its private set of file handles to refer to its open files. VFS maintains each client's open files in a table of open files, which is local to the servicing connection fibril. The table is composed of 'vfs_file_t'' pointers and the file handles index it. The associated connection fibril does not need to synchronize accesses to the table of open files because it is its exclusive owner. 103 104 The ''vfs_file_t'' structures track things like how many file handles reference it, the current position in the open file and the corresponding VFS node. The transition from a file handle to a VFS node is therefore straightforward.
