| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 2749 |
6011 d 15 h |
jermar |
/trunk/uspace/srv/vfs/ |
contents_rwlock should not be acquired as a futex but rather as a rwlock. |
|
| 2748 |
6011 d 15 h |
jermar |
/trunk/uspace/srv/vfs/ |
Support for O_TRUNC. |
|
| 2747 |
6012 d 14 h |
jermar |
/trunk/uspace/ |
Move the core lookup logic from TMPFS to libfs. |
|
| 2742 |
6014 d 14 h |
jermar |
/trunk/uspace/srv/ |
Separate creation of a TMPFS node and its linking in the file system name space.
Rename VFS_FREE to VFS_DESTROY and destroy_node() to unlink_node(). |
|
| 2740 |
6020 d 15 h |
jermar |
/trunk/uspace/srv/vfs/ |
Initialize the VFS node properly. |
|
| 2739 |
6020 d 15 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Remove duplicate initialization. |
|
| 2736 |
6022 d 17 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Unlink a TMPFS node more thoroughly. |
|
| 2735 |
6022 d 20 h |
jermar |
/trunk/uspace/ |
Support for rmdir(), unlink() and the respective VFS operations. |
|
| 2734 |
6022 d 22 h |
jermar |
/trunk/uspace/ |
Support for close(). |
|
| 2733 |
6022 d 22 h |
jermar |
/trunk/uspace/ |
Add TMPFS support for destroying leaf links in the file system namespace. |
|
| 2732 |
6022 d 23 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
When freeing up a TMPFS node, it should also be removed from the dentries hash table. |
|
| 2731 |
6022 d 23 h |
jermar |
/trunk/uspace/srv/ |
Add the VFS_FREE operation. This operation frees up whatever resources used by
a file system node for which there is no name (i.e. an unlinked node).
Cleanup VFS operations enums and remove unneeded VFS operations. |
|
| 2730 |
6024 d 1 h |
jermar |
/trunk/uspace/srv/ |
Introduce the notion of VFS node link counts. |
|
| 2728 |
6028 d 15 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Descend vs. descent. |
|
| 2711 |
6043 d 17 h |
jermar |
/trunk/uspace/ |
Remove the debugging hack from tmpfs_init(), which created several files and
directories on the filesystem. TMPFS is now self-sufficient enough to be able
to create its content via the standard VFS interface. |
|
| 2710 |
6043 d 18 h |
jermar |
/trunk/uspace/ |
VFS_WRITE and tmpfs_write fixes. |
|
| 2709 |
6043 d 20 h |
jermar |
/trunk/uspace/srv/vfs/ |
VFS_OPEN and VFS_WRITE now understand O_APPEND. |
|
| 2708 |
6043 d 20 h |
jermar |
/trunk/uspace/ |
VFS_OPEN now understands O_CREAT and O_EXCL. |
|
| 2707 |
6043 d 22 h |
jermar |
/trunk/uspace/ |
Support for mkdir(). |
|
| 2706 |
6044 d 2 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Move handling of the miss on excessive components out of the main loop in
tmpfs_lookup. |
|
| 2705 |
6044 d 14 h |
jermar |
/trunk/uspace/ |
More elegant, flexible and complete version of tmpfs_lookup. |
|
| 2704 |
6045 d 1 h |
jermar |
/trunk/uspace/srv/vfs/ |
Additional VFS lookup flags. |
|
| 2700 |
6051 d 23 h |
jermar |
/trunk/uspace/ |
Introduce the notion of lflag (i.e. lookup flags) to support the ability to
limit the scope of VFS node types that can be opened by open() and opendir(). In
the future, lflag will also specify actions for VFS_LOOKUP handlers that will be
carried out in situations such as the VFS node is not found (e.g. implementation
of mkdir() and open() with O_CREAT in oflag). |
|
| 2699 |
6052 d 13 h |
jermar |
/trunk/uspace/ |
Finish implementation of readdir(). Functions from this family are implemented
via using file descriptors for directories. For example, readdir() is
implemented as read() from an open directory. Of course, FS implementations
must understand that they are asked to read a directory and behave accordingly. |
|
| 2698 |
6052 d 19 h |
jermar |
/trunk/uspace/srv/vfs/ |
Small fix for VFS_TRUNCATE. Move lookup and registration code to separate
modules. |
|
| 2693 |
6057 d 23 h |
jermar |
/trunk/uspace/ |
Add ftruncate() and support for VFS_TRUNCATE to VFS and TMPFS. |
|
| 2691 |
6061 d 17 h |
jermar |
/trunk/uspace/srv/vfs/ |
Improve the API for converting (VFS triplets, size) to VFS nodes by introducing
a new type for results of vfs_lookup_internal(). |
|
| 2690 |
6062 d 15 h |
jermar |
/trunk/uspace/srv/ |
Make a distinction between VFS operations that are common to VFS and FS
implementations, operations that are VFS only and operations that are FS
implementations only. |
|
| 2689 |
6062 d 16 h |
jermar |
/trunk/uspace/srv/vfs/ |
Merge all VFS operations into one file. |
|
| 2688 |
6062 d 16 h |
jermar |
/trunk/uspace/ |
Make uspace rwlock API naming conventions consistent with kernel rwlock API. |
|
| 2687 |
6062 d 16 h |
jermar |
/trunk/uspace/srv/ |
Management of the cached VFS node size. |
|
| 2686 |
6062 d 17 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Previous commit was toxic. When emulating gaps, zero out the reallocated buffer, not the original one. |
|
| 2685 |
6062 d 17 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
TMPFS must handle file gaps. |
|
| 2684 |
6064 d 17 h |
jermar |
/trunk/ |
Add libc and VFS implementation of lseek(), VFS_SEEK resp.
Add the size member to the VFS node structure (not yet initialized). |
|
| 2683 |
6064 d 20 h |
jermar |
/trunk/uspace/srv/vfs/ |
Introduce the open file lock. Modify vfs_rdwr() to take this lock into account
when reading or writing from/to an open file. |
|
| 2682 |
6064 d 23 h |
jermar |
/trunk/uspace/ |
Fix type in declaration of VFS node rwlock.
Introduce a dedicated type for futexes. Make the existing futex code use this
newly introduced type and fix formatting in futex.c. |
|
| 2681 |
6065 d 0 h |
jermar |
/trunk/uspace/ |
Turn the namespace futex into rwlock. |
|
| 2680 |
6065 d 0 h |
jermar |
/trunk/uspace/ |
Add basic rwlock API for uspace so that VFS can be designed/implemented using
this API. So far, the implementation of this API merely wraps futexes into
rwlocks. Real rwlocks are wanted by ticket #54.
Using the new rwlock API, replace the VFS node content futex with an rwlock.
Lock the contents rwlock as reader on reads and as writer on writes. |
|
| 2679 |
6068 d 16 h |
jermar |
/trunk/uspace/srv/vfs/ |
Rename unlink_futex to namespace_futex and introduce a new futex for serializing
concurrent access to a VFS node's contents by multiple clients. |
|
| 2678 |
6070 d 19 h |
jermar |
/trunk/uspace/ |
The IPC_M_SHARE_* and IPC_M_DATA_* calls pass through 3 stages. Rename the send,
receive and deliver wrappers to names ending with 'start', 'receive' and
'finalize', respectively. This should make it clearer for dummies. |
|