| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 2682 |
5982 d 8 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 |
5982 d 9 h |
jermar |
/trunk/uspace/ |
Turn the namespace futex into rwlock. |
|
| 2680 |
5982 d 9 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 |
5986 d 2 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 |
5988 d 5 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. |
|
| 2677 |
5988 d 5 h |
jermar |
/trunk/ |
Rename IPC_M_AS_AREA_SEND to IPC_M_SHARE_OUT. Rename IPC_M_AS_AREA_RECV to
IPC_M_SHARE_IN. Provide user-friendly wrappers for these methods so that even
dummies can get it right. Some applications using simpler protocols still use
these methods directly. |
|
| 2676 |
5988 d 12 h |
jermar |
/trunk/ |
Simplify the IPC_M_DATA_WRITE protocol. Do not pass the source address space
virtual address to the recipient. This feature was not used anyway. Now
IPC_M_DATA_WRITE and IPC_M_DATA_READ are feature-aligned. |
|
| 2675 |
5989 d 0 h |
jermar |
/trunk/uspace/lib/libc/generic/ |
Actually use the nbyte argument in both read() and write().
Fix warnings in read() and write(). |
|
| 2674 |
5989 d 0 h |
jermar |
/trunk/uspace/ |
Add libc VFS wrapper for VFS_WRITE. Fix a small bug in read(). Place open(),
read() and write() declarations in their respective headers according to SUSv3. |
|
| 2673 |
5989 d 1 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Rename variable from 'size' to 'len'. |
|
| 2672 |
5989 d 1 h |
jermar |
/trunk/uspace/app/tester/vfs/ |
Use libc's VFS wrappers instead of direct communication with VFS. |
|
| 2671 |
5989 d 1 h |
jermar |
/trunk/uspace/lib/libc/ |
Add VFS wrappers for VFS_MOUNT, VFS_OPEN and VFS_READ to libc. |
|
| 2670 |
5993 d 0 h |
jermar |
/trunk/uspace/ |
Move the open(), read() and write() provided by streams.c away so that
these functions won't clash with the real open(), read() and write(), which are
soon to be provided by a libvfs library. Applications can now use open_stdin(),
open_stdout(), read_stdin() and write_stdout(). Later, there might be an option
of providing a custom console file system, which will work similarly to how
streams' open(), read() and write() worked. |
|
| 2669 |
5993 d 0 h |
jermar |
/trunk/uspace/lib/libc/generic/io/ |
Remove file.c. |
|
| 2668 |
5993 d 0 h |
jermar |
/trunk/uspace/lib/libc/include/io/ |
Remove file.h. |
|
| 2667 |
5993 d 21 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
The previous commit was not entirely sane.
Handle VFS_WRITE correctly when the file doesn't grow.
Handle it correctly also when the file grows. |
|
| 2666 |
5994 d 2 h |
jermar |
/trunk/uspace/srv/ |
VFS and TMPFS support for VFS_WRITE. |
|
| 2665 |
5995 d 23 h |
jermar |
/trunk/uspace/app/tester/vfs/ |
The vfs1 test now reads a file on a TMPFS file system. |
|
| 2664 |
5995 d 23 h |
jermar |
/trunk/uspace/srv/fs/tmpfs/ |
Fix two bugs in TMPFS-side VFS_READ. |
|
| 2663 |
5996 d 0 h |
jermar |
/trunk/uspace/ |
Reimplement VFS_READ using IPC_M_DATA_READ. |
|