uapi/linux/dm-log-userspace.h

15  * The device-mapper userspace log module consists of a kernel component and
17  * in dm-dirty-log.h.  Its purpose is simply to pass the parameters and
22  * dirty log API.  Each of these is described in more detail below.
50  * DM_ULOG_CTR corresponds to (found in dm-dirty-log.h):
51  * int (*ctr)(struct dm_dirty_log *log, struct dm_target *ti,
58  *	as the backing store for the log data.  'dm_get_device' will be called
61  *	for log data, 'data_size' in the dm_ulog_request struct should be 0.
64  * will be used by all request types to a specific log.  The constructor must
69  * data field with the log device if necessary, and setting 'data_size'
75  * DM_ULOG_DTR corresponds to (found in dm-dirty-log.h):
76  * void (*dtr)(struct dm_dirty_log *log);
84  * necessary to identify the log instance being destroyed.  There is no
94  * DM_ULOG_PRESUSPEND corresponds to (found in dm-dirty-log.h):
95  * int (*presuspend)(struct dm_dirty_log *log);
103  * necessary to identify the log instance being presuspended.  There is no
113  * DM_ULOG_POSTSUSPEND corresponds to (found in dm-dirty-log.h):
114  * int (*postsuspend)(struct dm_dirty_log *log);
122  * necessary to identify the log instance being postsuspended.  There is no
132  * DM_ULOG_RESUME corresponds to (found in dm-dirty-log.h):
133  * int (*resume)(struct dm_dirty_log *log);
141  * necessary to identify the log instance being resumed.  There is no
151  * DM_ULOG_GET_REGION_SIZE corresponds to (found in dm-dirty-log.h):
152  * __u32 (*get_region_size)(struct dm_dirty_log *log);
169  * DM_ULOG_IS_CLEAN corresponds to (found in dm-dirty-log.h):
170  * int (*is_clean)(struct dm_dirty_log *log, region_t region);
187  * DM_ULOG_IN_SYNC corresponds to (found in dm-dirty-log.h):
188  * int (*in_sync)(struct dm_dirty_log *log, region_t region,
202  * DM_ULOG_FLUSH corresponds to (found in dm-dirty-log.h):
203  * int (*flush)(struct dm_dirty_log *log);
215  * log, mark region requests are carried as payload in the flush request.
226  * DM_ULOG_MARK_REGION corresponds to (found in dm-dirty-log.h):
227  * void (*mark_region)(struct dm_dirty_log *log, region_t region);
245  * DM_ULOG_CLEAR_REGION corresponds to (found in dm-dirty-log.h):
246  * void (*clear_region)(struct dm_dirty_log *log, region_t region);
264  * DM_ULOG_GET_RESYNC_WORK corresponds to (found in dm-dirty-log.h):
265  * int (*get_resync_work)(struct dm_dirty_log *log, region_t *region);
282  * DM_ULOG_SET_REGION_SYNC corresponds to (found in dm-dirty-log.h):
283  * void (*set_region_sync)(struct dm_dirty_log *log,
301  * DM_ULOG_GET_SYNC_COUNT corresponds to (found in dm-dirty-log.h):
302  * region_t (*get_sync_count)(struct dm_dirty_log *log);
319  * DM_ULOG_STATUS_INFO corresponds to (found in dm-dirty-log.h):
320  * int (*status)(struct dm_dirty_log *log, STATUSTYPE_INFO,
335  * DM_ULOG_STATUS_TABLE corresponds to (found in dm-dirty-log.h):
336  * int (*status)(struct dm_dirty_log *log, STATUSTYPE_TABLE,
351  * DM_ULOG_IS_REMOTE_RECOVERING corresponds to (found in dm-dirty-log.h):
352  * int (*is_remote_recovering)(struct dm_dirty_log *log, region_t region);
411 	 * mirror log.  A single machine log could probably make due with
412 	 * just the 'luid', but a cluster-aware log must use the 'uuid' and
414 	 * communication concerning a particular log, but the 'luid' helps