File Manager

X7ROOT File Manager

Current Path: /usr/include/linux

📁 ..
📄 a.out.h(7.15 KB)
📄 acct.h(3.58 KB)
📄 adb.h(1.05 KB)
📄 adfs_fs.h(873 B)
📄 affs_hardblocks.h(1.45 KB)
📄 agpgart.h(3.83 KB)
📄 aio_abi.h(3.1 KB)
📄 apm_bios.h(3.46 KB)
📄 arcfb.h(150 B)
📄 atalk.h(960 B)
📄 atm.h(7.64 KB)
📄 atm_eni.h(585 B)
📄 atm_he.h(343 B)
📄 atm_idt77105.h(892 B)
📄 atm_nicstar.h(1.19 KB)
📄 atm_tcp.h(1.52 KB)
📄 atm_zatm.h(1.57 KB)
📄 atmapi.h(889 B)
📄 atmarp.h(1.2 KB)
📄 atmbr2684.h(3.13 KB)
📄 atmclip.h(513 B)
📄 atmdev.h(7.44 KB)
📄 atmioc.h(1.55 KB)
📄 atmlec.h(2.26 KB)
📄 atmmpc.h(4.07 KB)
📄 atmppp.h(576 B)
📄 atmsap.h(4.79 KB)
📄 atmsvc.h(1.75 KB)
📄 audit.h(18.03 KB)
📄 auto_fs.h(2.53 KB)
📄 auto_fs4.h(4.3 KB)
📄 auxvec.h(1.4 KB)
📄 ax25.h(2.7 KB)
📄 b1lli.h(1.62 KB)
📄 baycom.h(820 B)
📄 bfs_fs.h(1.79 KB)
📄 binfmts.h(565 B)
📄 blkpg.h(1.53 KB)
📄 blktrace_api.h(4.38 KB)
📄 bpf.h(22.04 KB)
📄 bpf_common.h(1.2 KB)
📄 bpf_perf_event.h(453 B)
📄 bpqether.h(952 B)
📄 bsg.h(2.37 KB)
📄 bt-bmc.h(508 B)
📄 btrfs.h(25.07 KB)
📁 byteorder
📁 caif
📁 can
📄 can.h(5.46 KB)
📄 capability.h(11.25 KB)
📄 capi.h(2.99 KB)
📄 cciss_defs.h(3.14 KB)
📄 cciss_ioctl.h(2.63 KB)
📄 cdrom.h(28.12 KB)
📄 cgroupstats.h(2.1 KB)
📄 chio.h(5.16 KB)
📄 cm4000_cs.h(1.68 KB)
📄 cn_proc.h(3.19 KB)
📄 coda.h(17.09 KB)
📄 coda_psdev.h(720 B)
📄 coff.h(12.12 KB)
📄 connector.h(2.14 KB)
📄 const.h(673 B)
📄 cramfs_fs.h(2.68 KB)
📄 cuda.h(842 B)
📄 cyclades.h(16.65 KB)
📄 cycx_cfm.h(2.86 KB)
📄 dcbnl.h(24.5 KB)
📄 dccp.h(6.22 KB)
📄 devlink.h(9.66 KB)
📄 dlm.h(2.43 KB)
📄 dlm_device.h(2.42 KB)
📄 dlm_netlink.h(1.04 KB)
📄 dlm_plock.h(831 B)
📄 dlmconstants.h(4.9 KB)
📄 dm-ioctl.h(10.55 KB)
📄 dm-log-userspace.h(14.82 KB)
📄 dn.h(4.42 KB)
📄 dqblk_xfs.h(8.72 KB)
📁 dvb
📄 edd.h(5.41 KB)
📄 efs_fs_sb.h(2.11 KB)
📄 elf-em.h(1.83 KB)
📄 elf-fdpic.h(1.04 KB)
📄 elf.h(12.69 KB)
📄 elfcore.h(2.86 KB)
📄 errno.h(23 B)
📄 errqueue.h(1.1 KB)
📄 ethtool.h(71.11 KB)
📄 eventpoll.h(1.76 KB)
📄 fadvise.h(779 B)
📄 falloc.h(2.72 KB)
📄 fanotify.h(3.52 KB)
📄 fb.h(16 KB)
📄 fcntl.h(2.16 KB)
📄 fd.h(11.31 KB)
📄 fdreg.h(5.23 KB)
📄 fib_rules.h(1.58 KB)
📄 fiemap.h(2.65 KB)
📄 filter.h(1.99 KB)
📄 firewire-cdev.h(42.86 KB)
📄 firewire-constants.h(3.16 KB)
📄 flat.h(2.04 KB)
📄 fou.h(617 B)
📄 fs.h(8.47 KB)
📄 fsl_hypervisor.h(7.05 KB)
📄 fuse.h(16.41 KB)
📄 futex.h(4.81 KB)
📄 gameport.h(834 B)
📄 gen_stats.h(1.5 KB)
📄 genetlink.h(1.82 KB)
📄 gfs2_ondisk.h(12 KB)
📄 gigaset_dev.h(1.35 KB)
📁 hdlc
📄 hdlc.h(574 B)
📄 hdlcdrv.h(2.78 KB)
📄 hdreg.h(22.11 KB)
📄 hid.h(1.79 KB)
📄 hiddev.h(6.13 KB)
📄 hidraw.h(1.41 KB)
📄 hpet.h(680 B)
📁 hsi
📄 hw_breakpoint.h(679 B)
📄 hyperv.h(10.22 KB)
📄 hysdn_if.h(1.29 KB)
📄 i2c-dev.h(2.37 KB)
📄 i2c.h(6.66 KB)
📄 i2o-dev.h(11.22 KB)
📄 i8k.h(1.4 KB)
📄 icmp.h(2.82 KB)
📄 icmpv6.h(3.82 KB)
📄 if.h(9.26 KB)
📄 if_addr.h(1.7 KB)
📄 if_addrlabel.h(658 B)
📄 if_alg.h(816 B)
📄 if_arcnet.h(3.63 KB)
📄 if_arp.h(6.3 KB)
📄 if_bonding.h(4.66 KB)
📄 if_bridge.h(6.46 KB)
📄 if_cablemodem.h(922 B)
📄 if_eql.h(1.26 KB)
📄 if_ether.h(7.25 KB)
📄 if_fc.h(1.63 KB)
📄 if_fddi.h(3.6 KB)
📄 if_frad.h(2.89 KB)
📄 if_hippi.h(4.07 KB)
📄 if_infiniband.h(1.13 KB)
📄 if_link.h(19.58 KB)
📄 if_ltalk.h(147 B)
📄 if_macsec.h(5.42 KB)
📄 if_packet.h(7.15 KB)
📄 if_phonet.h(361 B)
📄 if_plip.h(596 B)
📄 if_ppp.h(29 B)
📄 if_pppol2tp.h(3.18 KB)
📄 if_pppox.h(4.64 KB)
📄 if_slip.h(809 B)
📄 if_team.h(2.48 KB)
📄 if_tun.h(3.71 KB)
📄 if_tunnel.h(3.03 KB)
📄 if_vlan.h(1.69 KB)
📄 if_x25.h(817 B)
📄 ife.h(288 B)
📄 igmp.h(2.88 KB)
📁 iio
📄 in.h(9.36 KB)
📄 in6.h(6.97 KB)
📄 in_route.h(873 B)
📄 inet_diag.h(2.77 KB)
📄 inotify.h(2.85 KB)
📄 input.h(32.52 KB)
📄 ioctl.h(100 B)
📄 ip.h(3.47 KB)
📄 ip6_tunnel.h(1.67 KB)
📄 ip_vs.h(12.77 KB)
📄 ipc.h(1.99 KB)
📄 ipmi.h(14.63 KB)
📄 ipmi_msgdefs.h(3.21 KB)
📄 ipsec.h(884 B)
📄 ipv6.h(3.66 KB)
📄 ipv6_route.h(1.73 KB)
📄 ipx.h(1.79 KB)
📄 irda.h(7.31 KB)
📄 irqnr.h(104 B)
📁 isdn
📄 isdn.h(5.58 KB)
📄 isdn_divertif.h(1.11 KB)
📄 isdn_ppp.h(1.82 KB)
📄 isdnif.h(2.25 KB)
📄 iso_fs.h(6.29 KB)
📄 ivtv.h(2.89 KB)
📄 ivtvfb.h(1.12 KB)
📄 ixjuser.h(24.53 KB)
📄 jffs2.h(6.85 KB)
📄 joystick.h(3.5 KB)
📄 kd.h(6.04 KB)
📄 kdev_t.h(320 B)
📄 kernel-page-flags.h(788 B)
📄 kernel.h(375 B)
📄 kernelcapi.h(956 B)
📄 kexec.h(1.92 KB)
📄 keyboard.h(12.42 KB)
📄 keyctl.h(2.98 KB)
📄 kvm.h(33.89 KB)
📄 kvm_para.h(819 B)
📄 l2tp.h(4.98 KB)
📄 libc-compat.h(4.03 KB)
📄 limits.h(874 B)
📄 llc.h(2.98 KB)
📄 loop.h(2.31 KB)
📄 lp.h(3.72 KB)
📄 lwtunnel.h(839 B)
📄 magic.h(2.9 KB)
📄 major.h(4.48 KB)
📄 map_to_7segment.h(7.02 KB)
📄 matroxfb.h(1.37 KB)
📄 mdio.h(13.74 KB)
📄 media.h(3.5 KB)
📄 mei.h(4.62 KB)
📄 membarrier.h(7.71 KB)
📄 memfd.h(186 B)
📄 mempolicy.h(2.35 KB)
📄 meye.h(2.41 KB)
📄 mii.h(7.76 KB)
📄 minix_fs.h(2.01 KB)
📄 mman.h(230 B)
📁 mmc
📄 mmtimer.h(2.01 KB)
📄 mpls.h(1.33 KB)
📄 mqueue.h(2.01 KB)
📄 mroute.h(4.06 KB)
📄 mroute6.h(4.08 KB)
📄 msdos_fs.h(6.28 KB)
📄 msg.h(3.21 KB)
📄 mtio.h(7.92 KB)
📄 n_r3964.h(2.29 KB)
📄 nbd.h(2.34 KB)
📄 ncp.h(4.94 KB)
📄 ncp_fs.h(3.27 KB)
📄 ncp_mount.h(2.06 KB)
📄 ncp_no.h(651 B)
📄 ndctl.h(6.6 KB)
📄 neighbour.h(4.17 KB)
📄 net.h(1.97 KB)
📄 net_dropmon.h(1.07 KB)
📄 net_namespace.h(609 B)
📄 net_tstamp.h(4.06 KB)
📄 netconf.h(423 B)
📄 netdevice.h(1.46 KB)
📁 netfilter
📄 netfilter.h(1.6 KB)
📁 netfilter_arp
📄 netfilter_arp.h(380 B)
📁 netfilter_bridge
📄 netfilter_bridge.h(768 B)
📄 netfilter_decnet.h(1.83 KB)
📁 netfilter_ipv4
📄 netfilter_ipv4.h(2.02 KB)
📁 netfilter_ipv6
📄 netfilter_ipv6.h(2.04 KB)
📄 netlink.h(6.13 KB)
📄 netlink_diag.h(1005 B)
📄 netrom.h(744 B)
📄 nfc.h(7.72 KB)
📄 nfs.h(4.31 KB)
📄 nfs2.h(1.37 KB)
📄 nfs3.h(2.24 KB)
📄 nfs4.h(5.95 KB)
📄 nfs4_mount.h(1.83 KB)
📄 nfs_fs.h(1.51 KB)
📄 nfs_idmap.h(2.19 KB)
📄 nfs_mount.h(2.32 KB)
📄 nfsacl.h(605 B)
📁 nfsd
📄 nl80211.h(270.89 KB)
📄 nubus.h(8.17 KB)
📄 nvme_ioctl.h(1.55 KB)
📄 nvram.h(469 B)
📄 omap3isp.h(20.19 KB)
📄 omapfb.h(5.72 KB)
📄 oom.h(448 B)
📄 openvswitch.h(31.79 KB)
📄 packet_diag.h(1.5 KB)
📄 param.h(78 B)
📄 parport.h(3.56 KB)
📄 patchkey.h(829 B)
📄 pci.h(1.29 KB)
📄 pci_regs.h(50.79 KB)
📄 perf_event.h(31.96 KB)
📄 personality.h(1.99 KB)
📄 pfkeyv2.h(9.91 KB)
📄 pg.h(2.23 KB)
📄 phantom.h(1.55 KB)
📄 phonet.h(4.51 KB)
📄 pkt_cls.h(12.49 KB)
📄 pkt_sched.h(20.63 KB)
📄 pktcdvd.h(2.56 KB)
📄 pmu.h(5.13 KB)
📄 poll.h(22 B)
📄 posix_types.h(1.01 KB)
📄 ppdev.h(3.07 KB)
📄 ppp-comp.h(2.41 KB)
📄 ppp-ioctl.h(5.29 KB)
📄 ppp_defs.h(4.93 KB)
📄 pps.h(4.06 KB)
📄 prctl.h(6.75 KB)
📄 psample.h(735 B)
📄 ptp_clock.h(5.09 KB)
📄 ptrace.h(3.08 KB)
📄 qnx4_fs.h(2.21 KB)
📄 qnxtypes.h(561 B)
📄 quota.h(5.78 KB)
📄 radeonfb.h(297 B)
📁 raid
📄 random.h(1.2 KB)
📄 raw.h(302 B)
📄 rds.h(7.9 KB)
📄 reboot.h(1.25 KB)
📄 reiserfs_fs.h(712 B)
📄 reiserfs_xattr.h(470 B)
📄 resource.h(2.09 KB)
📄 rfkill.h(3.5 KB)
📄 romfs_fs.h(1.15 KB)
📄 rose.h(2.12 KB)
📄 route.h(2.21 KB)
📄 rtc.h(3.85 KB)
📄 rtnetlink.h(17.02 KB)
📄 scc.h(4.43 KB)
📄 sched.h(2.26 KB)
📄 screen_info.h(2.36 KB)
📄 sctp.h(29.53 KB)
📄 sdla.h(2.71 KB)
📄 seccomp.h(1.83 KB)
📄 securebits.h(2.58 KB)
📄 selinux_netlink.h(1.11 KB)
📄 sem.h(2.54 KB)
📄 serial.h(3.04 KB)
📄 serial_core.h(5.11 KB)
📄 serial_reg.h(15.66 KB)
📄 serio.h(1.81 KB)
📄 shm.h(2.19 KB)
📄 signal.h(171 B)
📄 signalfd.h(1.07 KB)
📄 snmp.h(12.42 KB)
📄 sock_diag.h(431 B)
📄 socket.h(738 B)
📄 sockios.h(5.83 KB)
📄 som.h(5.35 KB)
📄 sonet.h(2.17 KB)
📄 sonypi.h(5.12 KB)
📄 sound.h(1.15 KB)
📄 soundcard.h(44.96 KB)
📁 spi
📄 stat.h(1 KB)
📄 stddef.h(1 B)
📄 string.h(175 B)
📁 sunrpc
📄 suspend_ioctls.h(1.34 KB)
📄 swab.h(6.36 KB)
📄 synclink.h(8.71 KB)
📄 sysctl.h(25.46 KB)
📄 sysinfo.h(986 B)
📄 target_core_user.h(3.65 KB)
📄 taskstats.h(6.83 KB)
📁 tc_act
📁 tc_ematch
📄 tcp.h(5.93 KB)
📄 tcp_metrics.h(1.45 KB)
📄 telephony.h(8.84 KB)
📄 termios.h(443 B)
📄 time.h(1.54 KB)
📄 times.h(215 B)
📄 timex.h(6.17 KB)
📄 tiocl.h(1.63 KB)
📄 tipc.h(5.44 KB)
📄 tipc_config.h(14.1 KB)
📄 toshiba.h(1.24 KB)
📄 tty.h(1.33 KB)
📄 tty_flags.h(3.66 KB)
📄 types.h(1.4 KB)
📄 udf_fs_i.h(634 B)
📄 udp.h(1.28 KB)
📄 uhid.h(2.15 KB)
📄 uinput.h(5 KB)
📄 uio.h(668 B)
📄 ultrasound.h(4.39 KB)
📄 un.h(239 B)
📄 unistd.h(157 B)
📄 unix_diag.h(1.1 KB)
📁 usb
📄 usbdevice_fs.h(6.78 KB)
📄 userfaultfd.h(6.59 KB)
📄 utime.h(152 B)
📄 utsname.h(606 B)
📄 uuid.h(1.5 KB)
📄 uvcvideo.h(1.6 KB)
📄 v4l2-common.h(2.38 KB)
📄 v4l2-controls.h(37.34 KB)
📄 v4l2-dv-timings.h(25.75 KB)
📄 v4l2-mediabus.h(4.55 KB)
📄 v4l2-subdev.h(5.27 KB)
📄 version.h(332 B)
📄 veth.h(161 B)
📄 vfio.h(26.54 KB)
📄 vhost.h(7.13 KB)
📄 videodev2.h(67.36 KB)
📄 virtio_9p.h(1.99 KB)
📄 virtio_balloon.h(3.71 KB)
📄 virtio_blk.h(5.2 KB)
📄 virtio_config.h(3.34 KB)
📄 virtio_console.h(2.94 KB)
📄 virtio_gpu.h(8.23 KB)
📄 virtio_ids.h(2.32 KB)
📄 virtio_input.h(2.45 KB)
📄 virtio_net.h(9.5 KB)
📄 virtio_pci.h(6.63 KB)
📄 virtio_ring.h(6.18 KB)
📄 virtio_rng.h(265 B)
📄 virtio_scsi.h(5.13 KB)
📄 virtio_types.h(2.11 KB)
📄 virtio_vsock.h(3.01 KB)
📄 vm_sockets.h(5.13 KB)
📄 vsockmon.h(1.78 KB)
📄 vt.h(2.98 KB)
📄 vtpm_proxy.h(1.62 KB)
📄 wait.h(600 B)
📄 wanrouter.h(390 B)
📄 watchdog.h(2.22 KB)
📁 wimax
📄 wimax.h(8.17 KB)
📄 wireless.h(41.65 KB)
📄 wmi.h(1.84 KB)
📄 x25.h(3.42 KB)
📄 xattr.h(2.53 KB)
📄 xfrm.h(11 KB)

Editing: dm-log-userspace.h

/*
 * Copyright (C) 2006-2009 Red Hat, Inc.
 *
 * This file is released under the LGPL.
 */

#ifndef __DM_LOG_USERSPACE_H__
#define __DM_LOG_USERSPACE_H__

#include <linux/dm-ioctl.h> /* For DM_UUID_LEN */

/*
 * The device-mapper userspace log module consists of a kernel component and
 * a user-space component.  The kernel component implements the API defined
 * in dm-dirty-log.h.  Its purpose is simply to pass the parameters and
 * return values of those API functions between kernel and user-space.
 *
 * Below are defined the 'request_types' - DM_ULOG_CTR, DM_ULOG_DTR, etc.
 * These request types represent the different functions in the device-mapper
 * dirty log API.  Each of these is described in more detail below.
 *
 * The user-space program must listen for requests from the kernel (representing
 * the various API functions) and process them.
 *
 * User-space begins by setting up the communication link (error checking
 * removed for clarity):
 *	fd = socket(PF_NETLINK, SOCK_DGRAM, NETLINK_CONNECTOR);
 *	addr.nl_family = AF_NETLINK;
 *	addr.nl_groups = CN_IDX_DM;
 *	addr.nl_pid = 0;
 *	r = bind(fd, (struct sockaddr *) &addr, sizeof(addr));
 *	opt = addr.nl_groups;
 *	setsockopt(fd, SOL_NETLINK, NETLINK_ADD_MEMBERSHIP, &opt, sizeof(opt));
 *
 * User-space will then wait to receive requests form the kernel, which it
 * will process as described below.  The requests are received in the form,
 * ((struct dm_ulog_request) + (additional data)).  Depending on the request
 * type, there may or may not be 'additional data'.  In the descriptions below,
 * you will see 'Payload-to-userspace' and 'Payload-to-kernel'.  The
 * 'Payload-to-userspace' is what the kernel sends in 'additional data' as
 * necessary parameters to complete the request.  The 'Payload-to-kernel' is
 * the 'additional data' returned to the kernel that contains the necessary
 * results of the request.  The 'data_size' field in the dm_ulog_request
 * structure denotes the availability and amount of payload data.
 */

/*
 * DM_ULOG_CTR corresponds to (found in dm-dirty-log.h):
 * int (*ctr)(struct dm_dirty_log *log, struct dm_target *ti,
 *	      unsigned argc, char **argv);
 *
 * Payload-to-userspace:
 *	A single string containing all the argv arguments separated by ' 's
 * Payload-to-kernel:
 *	A NUL-terminated string that is the name of the device that is used
 *	as the backing store for the log data.  'dm_get_device' will be called
 *	on this device.  ('dm_put_device' will be called on this device
 *	automatically after calling DM_ULOG_DTR.)  If there is no device needed
 *	for log data, 'data_size' in the dm_ulog_request struct should be 0.
 *
 * The UUID contained in the dm_ulog_request structure is the reference that
 * will be used by all request types to a specific log.  The constructor must
 * record this association with the instance created.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field, filling the
 * data field with the log device if necessary, and setting 'data_size'
 * appropriately.
 */
#define DM_ULOG_CTR                    1

/*
 * DM_ULOG_DTR corresponds to (found in dm-dirty-log.h):
 * void (*dtr)(struct dm_dirty_log *log);
 *
 * Payload-to-userspace:
 *	A single string containing all the argv arguments separated by ' 's
 * Payload-to-kernel:
 *	None.  ('data_size' in the dm_ulog_request struct should be 0.)
 *
 * The UUID contained in the dm_ulog_request structure is all that is
 * necessary to identify the log instance being destroyed.  There is no
 * payload data.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and clearing
 * 'data_size' appropriately.
 */
#define DM_ULOG_DTR                    2

/*
 * DM_ULOG_PRESUSPEND corresponds to (found in dm-dirty-log.h):
 * int (*presuspend)(struct dm_dirty_log *log);
 *
 * Payload-to-userspace:
 *	None.
 * Payload-to-kernel:
 *	None.
 *
 * The UUID contained in the dm_ulog_request structure is all that is
 * necessary to identify the log instance being presuspended.  There is no
 * payload data.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and
 * 'data_size' appropriately.
 */
#define DM_ULOG_PRESUSPEND             3

/*
 * DM_ULOG_POSTSUSPEND corresponds to (found in dm-dirty-log.h):
 * int (*postsuspend)(struct dm_dirty_log *log);
 *
 * Payload-to-userspace:
 *	None.
 * Payload-to-kernel:
 *	None.
 *
 * The UUID contained in the dm_ulog_request structure is all that is
 * necessary to identify the log instance being postsuspended.  There is no
 * payload data.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and
 * 'data_size' appropriately.
 */
#define DM_ULOG_POSTSUSPEND            4

/*
 * DM_ULOG_RESUME corresponds to (found in dm-dirty-log.h):
 * int (*resume)(struct dm_dirty_log *log);
 *
 * Payload-to-userspace:
 *	None.
 * Payload-to-kernel:
 *	None.
 *
 * The UUID contained in the dm_ulog_request structure is all that is
 * necessary to identify the log instance being resumed.  There is no
 * payload data.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and
 * 'data_size' appropriately.
 */
#define DM_ULOG_RESUME                 5

/*
 * DM_ULOG_GET_REGION_SIZE corresponds to (found in dm-dirty-log.h):
 * uint32_t (*get_region_size)(struct dm_dirty_log *log);
 *
 * Payload-to-userspace:
 *	None.
 * Payload-to-kernel:
 *	uint64_t - contains the region size
 *
 * The region size is something that was determined at constructor time.
 * It is returned in the payload area and 'data_size' is set to
 * reflect this.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field appropriately.
 */
#define DM_ULOG_GET_REGION_SIZE        6

/*
 * DM_ULOG_IS_CLEAN corresponds to (found in dm-dirty-log.h):
 * int (*is_clean)(struct dm_dirty_log *log, region_t region);
 *
 * Payload-to-userspace:
 *	uint64_t - the region to get clean status on
 * Payload-to-kernel:
 *	int64_t  - 1 if clean, 0 otherwise
 *
 * Payload is sizeof(uint64_t) and contains the region for which the clean
 * status is being made.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - filling the payload with 0 (not clean) or
 * 1 (clean), setting 'data_size' and 'error' appropriately.
 */
#define DM_ULOG_IS_CLEAN               7

/*
 * DM_ULOG_IN_SYNC corresponds to (found in dm-dirty-log.h):
 * int (*in_sync)(struct dm_dirty_log *log, region_t region,
 *		  int can_block);
 *
 * Payload-to-userspace:
 *	uint64_t - the region to get sync status on
 * Payload-to-kernel:
 *	int64_t - 1 if in-sync, 0 otherwise
 *
 * Exactly the same as 'is_clean' above, except this time asking "has the
 * region been recovered?" vs. "is the region not being modified?"
 */
#define DM_ULOG_IN_SYNC                8

/*
 * DM_ULOG_FLUSH corresponds to (found in dm-dirty-log.h):
 * int (*flush)(struct dm_dirty_log *log);
 *
 * Payload-to-userspace:
 *	If the 'integrated_flush' directive is present in the constructor
 *	table, the payload is as same as DM_ULOG_MARK_REGION:
 *		uint64_t [] - region(s) to mark
 *	else
 *		None
 * Payload-to-kernel:
 *	None.
 *
 * If the 'integrated_flush' option was used during the creation of the
 * log, mark region requests are carried as payload in the flush request.
 * Piggybacking the mark requests in this way allows for fewer communications
 * between kernel and userspace.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and clearing
 * 'data_size' appropriately.
 */
#define DM_ULOG_FLUSH                  9

/*
 * DM_ULOG_MARK_REGION corresponds to (found in dm-dirty-log.h):
 * void (*mark_region)(struct dm_dirty_log *log, region_t region);
 *
 * Payload-to-userspace:
 *	uint64_t [] - region(s) to mark
 * Payload-to-kernel:
 *	None.
 *
 * Incoming payload contains the one or more regions to mark dirty.
 * The number of regions contained in the payload can be determined from
 * 'data_size/sizeof(uint64_t)'.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and clearing
 * 'data_size' appropriately.
 */
#define DM_ULOG_MARK_REGION           10

/*
 * DM_ULOG_CLEAR_REGION corresponds to (found in dm-dirty-log.h):
 * void (*clear_region)(struct dm_dirty_log *log, region_t region);
 *
 * Payload-to-userspace:
 *	uint64_t [] - region(s) to clear
 * Payload-to-kernel:
 *	None.
 *
 * Incoming payload contains the one or more regions to mark clean.
 * The number of regions contained in the payload can be determined from
 * 'data_size/sizeof(uint64_t)'.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and clearing
 * 'data_size' appropriately.
 */
#define DM_ULOG_CLEAR_REGION          11

/*
 * DM_ULOG_GET_RESYNC_WORK corresponds to (found in dm-dirty-log.h):
 * int (*get_resync_work)(struct dm_dirty_log *log, region_t *region);
 *
 * Payload-to-userspace:
 *	None.
 * Payload-to-kernel:
 *	{
 *		int64_t i; -- 1 if recovery necessary, 0 otherwise
 *		uint64_t r; -- The region to recover if i=1
 *	}
 * 'data_size' should be set appropriately.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field appropriately.
 */
#define DM_ULOG_GET_RESYNC_WORK       12

/*
 * DM_ULOG_SET_REGION_SYNC corresponds to (found in dm-dirty-log.h):
 * void (*set_region_sync)(struct dm_dirty_log *log,
 *			   region_t region, int in_sync);
 *
 * Payload-to-userspace:
 *	{
 *		uint64_t - region to set sync state on
 *		int64_t  - 0 if not-in-sync, 1 if in-sync
 *	}
 * Payload-to-kernel:
 *	None.
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and clearing
 * 'data_size' appropriately.
 */
#define DM_ULOG_SET_REGION_SYNC       13

/*
 * DM_ULOG_GET_SYNC_COUNT corresponds to (found in dm-dirty-log.h):
 * region_t (*get_sync_count)(struct dm_dirty_log *log);
 *
 * Payload-to-userspace:
 *	None.
 * Payload-to-kernel:
 *	uint64_t - the number of in-sync regions
 *
 * No incoming payload.  Kernel-bound payload contains the number of
 * regions that are in-sync (in a size_t).
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and
 * 'data_size' appropriately.
 */
#define DM_ULOG_GET_SYNC_COUNT        14

/*
 * DM_ULOG_STATUS_INFO corresponds to (found in dm-dirty-log.h):
 * int (*status)(struct dm_dirty_log *log, STATUSTYPE_INFO,
 *		 char *result, unsigned maxlen);
 *
 * Payload-to-userspace:
 *	None.
 * Payload-to-kernel:
 *	Character string containing STATUSTYPE_INFO
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and
 * 'data_size' appropriately.
 */
#define DM_ULOG_STATUS_INFO           15

/*
 * DM_ULOG_STATUS_TABLE corresponds to (found in dm-dirty-log.h):
 * int (*status)(struct dm_dirty_log *log, STATUSTYPE_TABLE,
 *		 char *result, unsigned maxlen);
 *
 * Payload-to-userspace:
 *	None.
 * Payload-to-kernel:
 *	Character string containing STATUSTYPE_TABLE
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and
 * 'data_size' appropriately.
 */
#define DM_ULOG_STATUS_TABLE          16

/*
 * DM_ULOG_IS_REMOTE_RECOVERING corresponds to (found in dm-dirty-log.h):
 * int (*is_remote_recovering)(struct dm_dirty_log *log, region_t region);
 *
 * Payload-to-userspace:
 *	uint64_t - region to determine recovery status on
 * Payload-to-kernel:
 *	{
 *		int64_t is_recovering;  -- 0 if no, 1 if yes
 *		uint64_t in_sync_hint;  -- lowest region still needing resync
 *	}
 *
 * When the request has been processed, user-space must return the
 * dm_ulog_request to the kernel - setting the 'error' field and
 * 'data_size' appropriately.
 */
#define DM_ULOG_IS_REMOTE_RECOVERING  17

/*
 * (DM_ULOG_REQUEST_MASK & request_type) to get the request type
 *
 * Payload-to-userspace:
 *	A single string containing all the argv arguments separated by ' 's
 * Payload-to-kernel:
 *	None.  ('data_size' in the dm_ulog_request struct should be 0.)
 *
 * We are reserving 8 bits of the 32-bit 'request_type' field for the
 * various request types above.  The remaining 24-bits are currently
 * set to zero and are reserved for future use and compatibility concerns.
 *
 * User-space should always use DM_ULOG_REQUEST_TYPE to acquire the
 * request type from the 'request_type' field to maintain forward compatibility.
 */
#define DM_ULOG_REQUEST_MASK 0xFF
#define DM_ULOG_REQUEST_TYPE(request_type) \
	(DM_ULOG_REQUEST_MASK & (request_type))

/*
 * DM_ULOG_REQUEST_VERSION is incremented when there is a
 * change to the way information is passed between kernel
 * and userspace.  This could be a structure change of
 * dm_ulog_request or a change in the way requests are
 * issued/handled.  Changes are outlined here:
 *	version 1:  Initial implementation
 *	version 2:  DM_ULOG_CTR allowed to return a string containing a
 *	            device name that is to be registered with DM via
 *	            'dm_get_device'.
 *	version 3:  DM_ULOG_FLUSH is capable of carrying payload for marking
 *		    regions.  This "integrated flush" reduces the number of
 *		    requests between the kernel and userspace by effectively
 *		    merging 'mark' and 'flush' requests.  A constructor table
 *		    argument ('integrated_flush') is required to turn this
 *		    feature on, so it is backwards compatible with older
 *		    userspace versions.
 */
#define DM_ULOG_REQUEST_VERSION 3

struct dm_ulog_request {
	/*
	 * The local unique identifier (luid) and the universally unique
	 * identifier (uuid) are used to tie a request to a specific
	 * mirror log.  A single machine log could probably make due with
	 * just the 'luid', but a cluster-aware log must use the 'uuid' and
	 * the 'luid'.  The uuid is what is required for node to node
	 * communication concerning a particular log, but the 'luid' helps
	 * differentiate between logs that are being swapped and have the
	 * same 'uuid'.  (Think "live" and "inactive" device-mapper tables.)
	 */
	uint64_t luid;
	char uuid[DM_UUID_LEN];
	char padding[3];        /* Padding because DM_UUID_LEN = 129 */

uint32_t version;       /* See DM_ULOG_REQUEST_VERSION */
	int32_t error;          /* Used to report back processing errors */

uint32_t seq;           /* Sequence number for request */
	uint32_t request_type;  /* DM_ULOG_* defined above */
	uint32_t data_size;     /* How much data (not including this struct) */

char data[0];
};

#endif /* __DM_LOG_USERSPACE_H__ */

X7ROOT File Manager

Editing: dm-log-userspace.h

Upload File

Create Folder