IBM Books

IBM General Parallel File System for AIX: Data Management API Guide

[ Bottom of Page | Previous Page | Next Page | Table of Contents | Index ]


DMAPI configuration attributes

The XDSM standard defines a set of configuration attributes, to be exported by each DMAPI implementation. These attributes specify which optional features are supported and give bounds on various resources.

The Data Management (DM) application can query the attribute values using the function dm_get_config. It can also query which events are supported, using the function dm_get_config_events.

The functions dm_get_config and dm_get_config_events receive a file handle (via arguments hanp and hlen). In GPFS, both functions ignore the handle, as the configuration is not dependent on the specific file or file system. This enables the DM application to query the configuration during initialization, when file handles may not yet be available.

Following are the attribute values that are used in GPFS:

Note:
To guarantee that the most current values are being used, the DM application should always query the configuration at runtime by using dm_get_config.


DM_CONFIG_BULKALL 1
DM_CONFIG_CREATE_BY_HANDLE 0
DM_CONFIG_DTIME_OVERLOAD 1
DM_CONFIG_LEGACY 1
DM_CONFIG_LOCK_UPGRADE 1
DM_CONFIG_MAX_ATTR_ON_DESTROY 1022
DM_CONFIG_MAX_ATTRIBUTE_SIZE 1022
DM_CONFIG_MAX_HANDLE_SIZE 16
DM_CONFIG_MAX_MANAGED_REGIONS 32
DM_CONFIG_MAX_MESSAGE_DATA 4096
DM_CONFIG_OBJ_REF 0
DM_CONFIG_PENDING 0
DM_CONFIG_PERS_ATTRIBUTES 1
DM_CONFIG_PERS_EVENTS 1
DM_CONFIG_PERS_INHERIT_ATTRIBS 0
DM_CONFIG_PERS_MANAGED_REGIONS 1
DM_CONFIG_PUNCH_HOLE 1
DM_CONFIG_TOTAL_ATTRIBUTE_SPACE 7168
DM_CONFIG_WILL_RETRY 0

Note:
DM_CONFIG_TOTAL_ATTRIBUTE_SPACE is per file. The entire space is available for opaque attributes. Non-opaque attributes (event list and managed regions) use separate space.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]