Структура атрибутов ввода/вывода (атрибутная запись)


#include <sys/iofunc.h>
typedef struct _iofunc_attr {
uint32_t flags;
int32_t lock_tid;
uint16_t lock_count;
uint16_t count;
uint16_t rcount;
uint16_t wcount;
uint16_t rlocks;
uint16_t wlocks;
struct _iofunc_mmap_list *mmap_list;
struct _iofunc_lock_list *lock_list;
void *list;
uint32_t list_size;
#if _FILE_OFFSET_BITS - 0 == 64
off_t nbytes;
ino_t inode;
off64_t nbytes;
ino64_t inode;
#elif _IOFUNC_OFFSET_BITS - 0 == 32
#if !defined(_FILE_OFFSET_BITS) || _FILE_OFFSET_BITS == 32
#if defined(__LITTLEENDIAN__)
off_t nbytes;
off_t nbytes_hi;
ino_t inode;
ino_t inode_hi;
#elif defined(__BIGENDIAN__)
off_t nbytes_hi;
off_t nbytes;
ino_t inode_hi;
ino_t inode;
#error endian not configured for system
#if defined(__LITTLEENDIAN__)
int32_t nbytes;
int32_t nbytes_hi;
int32_t inode;
int32_t inode_hi;
#elif defined(__BIGENDIAN__)
int32_t nbytes_hi;
int32_t nbytes;
int32_t inode_hi;
int32_t inode;
#error endian not configured for system
#error _IOFUNC_OFFSET_BITS value is unsupported
uid_t uid;
gid_t gid;
time_t mtime;
time_t atime;
time_t ctime;
mode_t mode;
nlink_t nlink;
dev_t rdev;
} iofunc_attr_t;


The iofunc_attr_t structure describes the attributes of the device that's associated with a resource manager. The members include the following:

A pointer a structure information about the mountpoint. By default, this structure is of type iofunc_mount_t, but you can specify your own structure by changing the IOFUNC_MOUNT_T manifest.
Flags that your resource manager can set to indicate the state of the device. This member is a combination of the following flags:
The access time is no longer valid. Typically set on a read from the resource.
The change of status time is no longer valid. Typically set on a file info change.
The number of links has changed.
The mode has changed.
The uid or the gid has changed.
The rdev member has changed, e.g. mknod().
The size has changed.
One or more of mtime, atime, or ctime has changed.
The modification time is no longer valid. Typically set on a write to the resource.

In addition to the above, your resource manager can use in any way the bits in the range defined by IOFUNC_ATTR_PRIVATE (see <sys/iofunc.h>).
The ID of the thread that has locked the attributes. To support multiple threads in your resource manager, you'll need to lock the attribute structure so that only one thread at a time is allowed to change it. The resource manager layer automatically locks the attribute (using iofunc_attr_lock()) for you when certain handler functions are called (i.e. IO_*).
The number of times the thread has locked the attribute structure. You can lock the attributes by calling iofunc_attr_lock() or iofunc_attr_trylock(); unlock them by calling iofunc_attr_unlock().

Note: A thread must unlock the attributes as many times as it locked them.

The number of OCBs using this attribute in any manner. When this count is zero, no one is using this attribute.
The number of OCBs using this attribute for reading.
The number of OCBs using this attribute for writing.
The number of read locks currently registered on the attribute.
The number of write locks currently registered on the attribute.
mmap_list and lock_list
To manage their particular functionality on the resource, the mmap_list member is used by iofunc_mmap() and iofunc_mmap_default(); the lock_list member is used by iofunc_lock_default(). Generally, you shouldn't need to modify or examine these members.
Reserved for future use.
Size of reserved area; reserved for future use.
The number of bytes in the resource; your resource manager can change this value. For a file, this would contain the file's size. For special devices (e.g. /dev/null) that don't support lseek() or have a radically different interpretation for lseek(), this field isn't used (because you wouldn't use any of the helper functions, but would supply your own instead.) In these cases, we recommend that you set this field to zero, unless there's a meaningful interpretation that you care to put to it.
This is a mountpoint-specific inode that must be unique per mountpoint. You can specify your own value, or 0 to have the Process manager fill it in for you. For filesystem type of applications, this may correspond to some on-disk structure. In any case, the interpretation of this field is up to you.
uid and gid
The user ID and group ID of the owner of this resource. These fields are updated automatically by the chown() helper functions (e.g. iofunc_chown_default()) and are referenced in conjunction with the mode member for access-granting purposes by the open() help functions (e.g. iofunc_open_default()).
mtime, atime, and ctime
POSIX time members:
modification time ( write() updates this).
access time ( read() updates this).
change of status time ( write(), chmod() and chown() update this).

Note: One or more of the three time members may be invalidated as a result of calling an iofunc-layer function. To see if a time member is invalid, check the flags member. This is to avoid having each and every I/O message handler go to the kernel and request the current time of day, just to fill in the attribute structure's time member(s).

To fill the members with the correct time, call iofunc_time_update().
The resource's mode (e.g. type, permissions). Valid modes may be selected from the S_* series of constants in <sys/stat.h>; see Access permissions.
The number of links to this particular name; your resource manager can modify this member. For names that represent a directory, this value must be at least 2 (one for the directory itself, one for the ./ entry in it).
The device number for a character special device and the rdev number for a named special device.


ЗОСРВ «Нейтрино»

Тематические ссылки:

time_t, iofunc_attr_lock(), iofunc_attr_trylock(), iofunc_attr_unlock(), iofunc_lock_default(), iofunc_mmap(), iofunc_mmap_default(), iofunc_ocb_t, iofunc_time_update()

Предыдущий раздел: Описание API системной библиотеки