mirror of
https://github.com/genodelabs/genode.git
synced 2024-12-22 06:57:51 +00:00
ae1d0c04ae
This patch introduces the file-system-session interface, provides an implementation of this interface in the form of an in-memory file system, and enables the libc to use the new file-system facility. The new interface resides in 'os/include/file_system_session/'. It uses synchronous RPC calls for functions referring to directory and meta-data handling. For transferring payload from/to files, the packet-stream interface is used. I envision that the asynchronous design of the packet-stream interface fits well will the block-session interface. Compared to Unix-like file-system APIs, Genode's file-system session interface is much simpler. In particular, it does not support per-file permissions. On Genode, we facilitate binding policy (such as write-permission) is sessions rather than individual file objects. As a reference implementation of the new interface, there is the new 'ram_fs' service at 'os/src/server/ram_fs'. It stores sparse files in memory. At the startup, 'ram_fs' is able to populate the file-system content with directories and ROM modules as specified in its configuration. To enable libc-using programs to access the new file-system interface, there is the new libc plugin at 'libports/src/lib/libc-fs'. Using this plugin, files stored on a native Genode file system can be accessed using the traditional POSIX file API. To see how the three parts described above fit together, the test case at 'libports/run/libc_fs' can be taken as reference. It reuses the original 'libc_ffat' test to exercise several file operations on a RAM file-system using the libc API. :Known limitations: The current state should be regarded as work in progress. In particular the error handling is not complete yet. Not all of the session functions return the proper exceptions in the event of an error. I plan to successively refine the interface while advancing the file-system implementations. Also the support for truncating files and symlink handling are not yet implemented. Furthermore, there is much room for optimization, in particular for the handling of directory entries. Currently, we communicate only one dir entry at a time, which is bad when traversing large trees. However, I decided to focus on functionality first and defer optimizations (such as batching dir entries) to a later stage. The current implementation does not handle file modification times at all, which may be a severe limitation for tools that depend on this information such as GNU make. Support for time will be added after we have revisited Genode's timer-session interface (issue #1). Fixes #54 Fixes #171 |
||
|---|---|---|
| .. | ||
| arm | ||
| x86_32 | ||
| x86_64 | ||
| ffat_block.mk | ||
| freetype.mk | ||
| gallium-aux.mk | ||
| gallium-egl.mk | ||
| gallium-failover.mk | ||
| gallium-i915.mk | ||
| gallium-identity.mk | ||
| gallium-softpipe.mk | ||
| gallium-trace.mk | ||
| gallium.inc | ||
| gallium.mk | ||
| gmp-mpf.mk | ||
| gmp-mpq.mk | ||
| gmp-mpz.mk | ||
| gmp.inc | ||
| gmp.mk | ||
| history.mk | ||
| jbig2dec.mk | ||
| jpeg.mk | ||
| libc_ffat.mk | ||
| libc_fs.mk | ||
| libc_lock_pipe.mk | ||
| libc_log.mk | ||
| libc_lwip_loopback.mk | ||
| libc_lwip_nic_dhcp.mk | ||
| libc_lwip.mk | ||
| libc_rom.mk | ||
| libc_terminal.mk | ||
| libc-common.inc | ||
| libc-compat.mk | ||
| libc-gdtoa.mk | ||
| libc-gen.inc | ||
| libc-inet.mk | ||
| libc-locale.mk | ||
| libc-regex.mk | ||
| libc-stdio.mk | ||
| libc-stdlib.mk | ||
| libc-stdtime.mk | ||
| libc-string.mk | ||
| libc.mk | ||
| libdrm.mk | ||
| libm.mk | ||
| libpng.mk | ||
| lwip.mk | ||
| mesa-egl.mk | ||
| mesa.inc | ||
| mesa.mk | ||
| mpfr.mk | ||
| mupdf.mk | ||
| ncurses.mk | ||
| openjpeg.mk | ||
| pthread.mk | ||
| python.inc | ||
| readline.mk | ||
| sdl.mk | ||
| test-ldso2.mk | ||
| test-ldso.mk | ||
| zlib.mk | ||