Searched refs:DLM (Results 1 – 21 of 21) sorted by relevance
/linux-4.4.14/fs/dlm/ |
D | Kconfig | 1 menuconfig DLM config 2 tristate "Distributed Lock Manager (DLM)" 11 bool "DLM debugging" 12 depends on DLM
|
/linux-4.4.14/fs/gfs2/ |
D | Kconfig | 23 you want to use the DLM, be sure to enable IPv4/6 networking. 26 bool "GFS2 DLM locking" 28 CONFIGFS_FS && SYSFS && (DLM=y || DLM=GFS2_FS) 33 interface between GFS2 and the DLM, which is required to use GFS2
|
/linux-4.4.14/Documentation/filesystems/ |
D | dlmfs.txt | 3 A minimal DLM userspace interface implemented via a virtual file 24 - Right now it only works with the OCFS2 DLM, though support for other 25 DLM implementations should not be a major issue. 56 Once you're heartbeating, DLM lock 'domains' can be easily created / 67 request for an already acquired lock will not generate another DLM 80 OCFS2 DLM limitation). Through this mechanism, users of dlmfs can share
|
D | gfs2-glocks.txt | 11 threads from making calls to the DLM, etc. at the same time. If a 25 to the following DLM lock modes: 27 Glock mode | DLM lock mode 29 UN | IV/NL Unlocked (no DLM lock associated with glock) or NL 64 go_callback | Called if the DLM sends a callback to drop this lock 150 1. DLM lock time (non-blocking requests) 151 2. DLM lock time (blocking requests) 152 3. Inter-request time (again to the DLM) 155 away, whatever the state of the DLM lock in question. That
|
D | 00-INDEX | 47 - info on the userspace interface to the OCFS2 DLM.
|
/linux-4.4.14/Documentation/ |
D | md-cluster.txt | 29 2. DLM Locks for management 39 number is based on the slot number returned by the DLM subsystem. Since 40 DLM starts node count from one and bitmap slots start from zero, one is 41 subtracted from the DLM slot number to arrive at the bitmap slot number. 61 The DLM LVB is used to communicate within nodes of the cluster. There 126 When a node fails, the DLM informs the cluster with the slot. The node
|
/linux-4.4.14/arch/frv/kernel/ |
D | debug-stub.c | 221 __UART0(DLM) = (value >> 8) & 0xff; in console_set_baud() 240 value = __UART0(DLM) << 8; in console_get_baud()
|
D | gdb-io.c | 101 __UART(DLM) = (value >> 8) & 0xff; in gdbstub_set_baud()
|
/linux-4.4.14/fs/ocfs2/ |
D | Kconfig | 41 depends on OCFS2_FS && DLM 45 in conjunction with the DLM in fs/dlm. If you are using a
|
/linux-4.4.14/arch/arm/mach-orion5x/ |
D | tsx09-common.c | 38 writel((divisor >> 8) & 0xff, UART1_REG(DLM)); in qnap_tsx09_power_off()
|
D | terastation_pro2-setup.c | 281 writel((divisor >> 8) & 0xff, UART1_REG(DLM)); in tsp2_power_off()
|
D | kurobox_pro-setup.c | 302 writel((divisor >> 8) & 0xff, UART1_REG(DLM)); in kurobox_pro_power_off()
|
/linux-4.4.14/drivers/usb/serial/ |
D | io_16654.h | 44 #define DLM 9 // Bank2[ 1 ] Divisor Latch MSB macro
|
D | io_edgeport.c | 2270 MAKE_CMD_WRITE_REG(&currCmd, &cmdLen, number, DLM, HIGH8(divisor)); in send_cmd_write_baud_rate()
|
/linux-4.4.14/drivers/power/reset/ |
D | qnap-poweroff.c | 67 writel((divisor >> 8) & 0xff, UART1_REG(DLM)); in qnap_power_off()
|
/linux-4.4.14/fs/ocfs2/cluster/ |
D | masklog.c | 123 define_mask(DLM),
|
/linux-4.4.14/drivers/net/hamradio/ |
D | baycom_ser_fdx.c | 117 #define DLM(iobase) (iobase+1) macro 189 outb(divisor >> 8, DLM(dev->base_addr)); in ser12_set_divisor()
|
D | baycom_ser_hdx.c | 105 #define DLM(iobase) (iobase+1) macro 176 outb(0, DLM(dev->base_addr)); in ser12_set_divisor()
|
D | yam.c | 175 #define DLM(iobase) (iobase+1) macro 311 outb(0, DLM(iobase)); in fpga_reset() 483 outb(0, DLM(dev->base_addr)); in yam_set_uart()
|
/linux-4.4.14/drivers/md/ |
D | Kconfig | 183 depends on DLM
|
/linux-4.4.14/ |
D | MAINTAINERS | 3518 DISTRIBUTED LOCK MANAGER (DLM)
|