Changeset c142f5b in rtems-docs


Ignore:
Timestamp:
Jan 16, 2016, 2:48:19 PM (4 years ago)
Author:
Amar Takhar <verm@…>
Branches:
4.11, master
Children:
2d1dc3f
Parents:
9e27b86
git-author:
Amar Takhar <verm@…> (01/16/16 14:48:19)
git-committer:
Amar Takhar <verm@…> (05/03/16 00:51:22)
Message:

Fix markup warnings.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • filesystem/filesystem.rst

    r9e27b86 rc142f5b  
    16531653    Figure of the IMFS Memfile control blocks
    16541654
    1655 .. _File-and-Directory-Removal-Constraints:
    16561655
    16571656File and Directory Removal Constraints
     
    18071806
    18081807# File control block - rtems_libio_t structure
     1808
    18091809  .. code:: c
     1810
    18101811      struct rtems_libio_tt {
    18111812      rtems_driver_name_t              \*driver;
     
    18201821      rtems_filesystem_file_handlers_r  handlers;
    18211822      };
     1823
    18221824  A file control block can exist for regular files, devices and directories.
    18231825  The following fields are important for regular file and directory access:
     1826
    18241827  - Size - For a file this represents the number of bytes currently
    18251828    stored in a file. For a directory this field is not filled in.
     1829
    18261830  - Offset - For a file this is the byte file position index relative to
    18271831    the start of the file. For a directory this is the byte offset into a
    18281832    sequence of dirent structures.
     1833
    18291834  - Pathinfo - This is a structure that provides a pointer to node
    18301835    information, OPS table functions, Handler functions and the mount table
    18311836    entry associated with this node.
     1837
    18321838  - file_info - A pointer to node information that is used by Handler
    18331839    functions
     1840
    18341841  - handlers - A pointer to a table of handler functions that operate on
    18351842    a file, device or directory through a file descriptor index
     
    18401847The rtems_filesystem_location_info_tt structure below provides sufficient
    18411848information to process nodes under a mounted filesystem.
     1849
    18421850.. code:: c
    18431851
     
    18731881general developmental information on each of the functions contained in this
    18741882function management structure.
     1883
    18751884.. code:: c
    18761885
     
    27672776    is this contains a structure that is unique to file type (See IMFS_typs_union
    27682777    in imfs.h).
     2778
    27692779    - IMFS_DIRECTORY
     2780
    27702781      An IMFS directory contains a dynamic chain structure that
    27712782      records all files and directories that are subordinate to the directory node.
     2783
    27722784    - IMFS_MEMORY_FILE
     2785
    27732786      Under the in memory filesystem regular files hold data. Data is dynamically
    27742787      allocated to the file in 128 byte chunks of memory.  The individual chunks of
     
    27772790      are used to record the locations of all segments of the file.  The
    27782791      memory organization of an IMFS file are discussed elsewhere in this manual.
     2792
    27792793    - IMFS_HARD_LINK
     2794
    27802795      The IMFS filesystem supports the concept of hard links to other nodes in the
    27812796      IMFS filesystem.  These hard links are actual pointers to other nodes in the
    27822797      same filesystem. This type of link cannot cross-filesystem boundaries.
     2798
    27832799    - IMFS_SYM_LINK
     2800
    27842801      The IMFS filesystem supports the concept of symbolic links to other nodes in
    27852802      any filesystem. A symbolic link consists of a pointer to a character string
     
    27872804      cross-filesystem boundaries.  Just as with most versions of UNIX supporting
    27882805      symbolic links, a symbolic link can point to a non-existent file.
     2806
    27892807    - IMFS_DEVICE
     2808
    27902809      All RTEMS devices now appear as files under the in memory filesystem. On
    27912810      system initialization, all devices are registered as nodes under the file
     
    28102829
    28112830The IMFS conforms to the general filesystem requirements for node
    2812 removal.  See :ref:`File and Directory Removal Constraints <File-and-Directory-Removal-Constraints>`.
     2831removal.  See `File and Directory Removal Constraints`_.
    28132832
    28142833IMFS General Housekeeping Notes
Note: See TracChangeset for help on using the changeset viewer.