lvm2/libdm/.exported_symbols.DM_1_02_138

dm_bitset_parse_list
dm_bit_get_last
dm_bit_get_prev
dm_filemapd_mode_from_string
dm_stats_bind_from_fd
dm_stats_start_filemapd
dm_stats_update_regions_from_fd
dm_tree_node_add_cache_target
dm_tree_node_add_raid_target_with_params_v2
symver: sorting 2021-04-04 12:26:45 +03:00			`dm_bitset_parse_list`
libdm: add dm_bit_get_last()/dm_bit_get_prev() It is sometimes convenient to iterate over the set bits in a dm bitset in reverse order (from the highest set bit toward zero), or to quickly find the last set bit. Add dm_bit_get_last() and dm_bit_get_prev(), mirroring the existing dm_bit_get_first() and dm_bit_get_next(). dm_bit_get_prev() uses __builtin_clz when available to efficiently test the bitset in reverse. 2016-12-11 15:44:45 +03:00			`dm_bit_get_last`
			`dm_bit_get_prev`
daemons: add dmfilemapd Add a daemon that can be launched to monitor a group of regions corresponding to the extents of a file, and to update the regions as the file's allocation changes. The daemon is intended to be started from a library interface, but can also be run from the command line: dmfilemapd <fd> <group_id> <path> <mode> [<foreground>[<log_level>]] Where fd is a file descriptor open on the mapped file, group_id is the group identifier of the mapped group and mode is either "inode" or "path". E.g.: # dmfilemapd 3 0 vm.img inode 1 3 3<vm.img ... If foreground is non-zero, the daemon will not fork to run in the background. If verbose is non-zero, libdm and daemon log messages will be printed. It is possible for the group identifier to change when regions are re-mapped: this occurs when the group leader is deleted (regroup=1 in dm_stats_update_regions_from_fd()), and another region is created before the daemon has a chance to recreate the leader region. The operation is inherently racey since there is currently no way to atomically move or resize a dm_stats region while retaining its region_id. Detect this condition and update the group_id value stored in the filemap monitor. A function is also provided in the the stats API to launch the filemap monitoring daemon: int dm_stats_start_filemapd(int fd, uint64_t group_id, const char *path, dm_filemapd_mode_t mode, unsigned foreground, unsigned verbose); This carries out the first fork and execs dmfilemapd with the arguments specified. A dm_filemapd_mode_t value is specified by the mode argument: either DM_FILEMAPD_FOLLOW_INODE, or DM_FILEMAPD_FOLLOW_PATH. A helper function, dm_filemapd_mode_from_string(), is provided to parse a string containing a valid mode name into the appropriate dm_filemapd_mode_t value. 2016-12-15 23:10:27 +03:00			`dm_filemapd_mode_from_string`
libdm: add dm_stats_bind_from_fd() dmsetup already has a version of this function, and dmfilemapd will need it too: move it to libdevmapper to avoid copying it around. 2016-12-18 17:40:57 +03:00			`dm_stats_bind_from_fd`
daemons: add dmfilemapd Add a daemon that can be launched to monitor a group of regions corresponding to the extents of a file, and to update the regions as the file's allocation changes. The daemon is intended to be started from a library interface, but can also be run from the command line: dmfilemapd <fd> <group_id> <path> <mode> [<foreground>[<log_level>]] Where fd is a file descriptor open on the mapped file, group_id is the group identifier of the mapped group and mode is either "inode" or "path". E.g.: # dmfilemapd 3 0 vm.img inode 1 3 3<vm.img ... If foreground is non-zero, the daemon will not fork to run in the background. If verbose is non-zero, libdm and daemon log messages will be printed. It is possible for the group identifier to change when regions are re-mapped: this occurs when the group leader is deleted (regroup=1 in dm_stats_update_regions_from_fd()), and another region is created before the daemon has a chance to recreate the leader region. The operation is inherently racey since there is currently no way to atomically move or resize a dm_stats region while retaining its region_id. Detect this condition and update the group_id value stored in the filemap monitor. A function is also provided in the the stats API to launch the filemap monitoring daemon: int dm_stats_start_filemapd(int fd, uint64_t group_id, const char *path, dm_filemapd_mode_t mode, unsigned foreground, unsigned verbose); This carries out the first fork and execs dmfilemapd with the arguments specified. A dm_filemapd_mode_t value is specified by the mode argument: either DM_FILEMAPD_FOLLOW_INODE, or DM_FILEMAPD_FOLLOW_PATH. A helper function, dm_filemapd_mode_from_string(), is provided to parse a string containing a valid mode name into the appropriate dm_filemapd_mode_t value. 2016-12-15 23:10:27 +03:00			`dm_stats_start_filemapd`
symver: sorting 2021-04-04 12:26:45 +03:00			`dm_stats_update_regions_from_fd`
libdm: maintain binary interface for new FEATURE flag Older library version was not detecting unknown 'feature' bits and could let start target without needed option. New versioned symbol now checks for supported feature bits. _Base version keeps accepting only previously known features and mask/ignores unknown bits. NB: if the older binary passed in 'random' bits, it will not get metadata2 by chance. New linked binary get new validation function. Library user is required to not pass 'trash' for unsupported bits, as such calls will be rejected. 2017-02-25 00:41:42 +03:00			`dm_tree_node_add_cache_target`
symver: sorting 2021-04-04 12:26:45 +03:00			`dm_tree_node_add_raid_target_with_params_v2`