Home
last modified time | relevance | path

Searched refs:MD (Results 1 – 25 of 42) sorted by relevance

12

/Linux-v4.19/drivers/scsi/aic94xx/
Daic94xx_dump.c42 #define MD(x) (1 << (x)) macro
52 {"LmMnSCBPTR", 0x20, 16, MD(0)|MD(1)|MD(2)|MD(3)|MD(4) },
53 {"LmMnDDBPTR", 0x22, 16, MD(0)|MD(1)|MD(2)|MD(3)|MD(4) },
61 {"LmMnDMAERRS", 0x46, 8, MD(0)|MD(1) },
62 {"LmMnSGDMAERRS", 0x47, 8, MD(0)|MD(1) },
63 {"LmMnEXPHDRP", 0x48, 8, MD(0) },
64 {"LmMnSASAALIGN", 0x48, 8, MD(1) },
65 {"LmMnMSKHDRP", 0x49, 8, MD(0) },
66 {"LmMnSTPALIGN", 0x49, 8, MD(1) },
67 {"LmMnRCVHDRP", 0x4A, 8, MD(0) },
[all …]
/Linux-v4.19/Documentation/md/
Draid5-cache.txt27 unclean shutdown. We call an array degraded if it has inconsistent data. MD
34 two-step write will guarantee MD can recover correct data after unclean
37 In write-through mode, MD reports IO completion to upper layer (usually
51 write. For non-full-stripe writes, MD must read old data before the new parity
59 In write-back mode, MD reports IO completion to upper layer (usually
64 In write-back mode, MD also caches data in memory. The memory cache includes
83 checksum is an optimization because MD can write meta and data freely without
84 worry about the order. MD superblock has a field pointed to the valid meta data
88 order in which MD writes data to cache disk and RAID disks. Specifically, in
89 write-through mode, MD calculates parity for IO data, writes both IO data and
[all …]
/Linux-v4.19/arch/um/scripts/
DMakefile.rules12 …c_flags = -Wp,-MD,$(depfile) $(USER_CFLAGS) -include $(srctree)/include/linux/kern_levels.h -inclu…
19 c_flags = -Wp,-MD,$(depfile) $(call unprofile,$(USER_CFLAGS)) $(CFLAGS_$(basetarget).o)
/Linux-v4.19/tools/build/
DBuild.include26 # The temporary file to save gcc -MD generated dependencies must not
93 c_flags_1 = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(CFLAGS) -D"BUILD_STR(s)=\#s" $(CFLAGS_$(basetarget).o) …
96 cxx_flags = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(CXXFLAGS) -D"BUILD_STR(s)=\#s" $(CXXFLAGS_$(basetarget)…
101 host_c_flags = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(KBUILD_HOSTCFLAGS) -D"BUILD_STR(s)=\#s" $(HOSTCFLAGS…
/Linux-v4.19/arch/sh/kernel/cpu/sh2a/
Dentry.S49 bld.b #6,@(0,r2) !previus SR.MD
50 bst.b #6,@(4*4,r15) !set cpu mode to SR.MD
53 bset.b #6,@(0,r2) !set SR.MD
215 shlr2 r1 ! clear MD bit
241 ! bit30 = MD (compatible SH3/4)
/Linux-v4.19/scripts/
DMakefile.lib154 c_flags = -Wp,-MD,$(depfile) $(NOSTDINC_FLAGS) $(LINUXINCLUDE) \
159 a_flags = -Wp,-MD,$(depfile) $(NOSTDINC_FLAGS) $(LINUXINCLUDE) \
162 cpp_flags = -Wp,-MD,$(depfile) $(NOSTDINC_FLAGS) $(LINUXINCLUDE) \
169 dtc_cpp_flags = -Wp,-MD,$(depfile).pre.tmp -nostdinc \
DMakefile.host78 hostc_flags = -Wp,-MD,$(depfile) $(__hostc_flags)
79 hostcxx_flags = -Wp,-MD,$(depfile) $(__hostcxx_flags)
/Linux-v4.19/net/nsh/
DKconfig7 only MD type 1 and only with the openvswitch module.
/Linux-v4.19/Documentation/devicetree/bindings/display/panel/
Durt,umsh-8596md.txt1 United Radiant Technology UMSH-8596MD-xT 7.0" WVGA TFT LCD panel
/Linux-v4.19/Documentation/filesystems/
Dntfs.txt15 - The Software RAID / MD driver
16 - Limitations when using the MD driver
34 use the kernel's Software RAID / MD driver. See section "Using Software RAID
232 Device-Mapper driver or the kernel's Software RAID / MD driver. The former is
249 Software RAID / MD driver for raid level 5, see the next section for details.
377 The Software RAID / MD driver
381 Software RAID / MD driver. For which you need to set up your /etc/raidtab
386 the MD driver with NTFS volumes" especially if you want to use linear raid).
392 superblock used by the MD driver would damage the NTFS volume.
415 Note for stripe sets with parity you will also need to tell the MD driver
[all …]
/Linux-v4.19/drivers/md/
DKconfig5 menuconfig MD config
13 if MD
88 an error free MD (multiple device) to the higher levels of the
164 the MD framework. It is not under active development. New
171 tristate "Faulty test module for MD"
181 tristate "Cluster Support for MD"
186 Clustering support for MD devices. This enables locking and
188 nodes in the cluster can access the MD devices simultaneously.
562 endif # MD
/Linux-v4.19/arch/sh/kernel/cpu/sh2/
Dentry.S59 or r0,r3 ! set MD
292 and r1,r3 ! copy MD bit
294 shll2 r1 ! clear MD bit
355 ! bit30 = MD (compatible SH3/4)
/Linux-v4.19/arch/sh/kernel/
Dhead_32.S62 mov.l 1f, r0 ! MD=1, RB=0, BL=0, IMASK=0xF
343 1: .long 0x500080F0 ! MD=1, RB=0, BL=1, FD=1, IMASK=0xF
/Linux-v4.19/drivers/mfd/
Dssbi.c50 #define SET_SSBI_MODE2_REG_ADDR_15_8(MD, AD) \ argument
51 (((MD) & 0x0F) | ((((AD) >> 8) << SSBI_MODE2_REG_ADDR_15_8_SHFT) & \
/Linux-v4.19/arch/x86/um/
DMakefile40 $(obj)/user-offsets.s: c_flags = -Wp,-MD,$(depfile) $(USER_CFLAGS) \
/Linux-v4.19/arch/s390/purgatory/
DMakefile24 KBUILD_CFLAGS += -c -MD -Os -m64 -msoft-float -fno-common
/Linux-v4.19/Documentation/device-mapper/
Ddm-raid.txt4 The device-mapper RAID (dm-raid) target provides a bridge from DM to MD.
5 It allows the MD RAID drivers to be accessed using a device-mapper
155 MD personalities supporting such device addition will read the data from
185 1.9.0 supports up to 253 which is enforced by the used MD kernel runtime.
329 1.7.0 Add support for MD RAID0 mappings.
346 1.12.1 Fix for MD deadlock between mddev_suspend() and md_write_start() available
/Linux-v4.19/drivers/net/wan/
DMakefile53 …$(CPP) -D__ASSEMBLY__ -Wp,-MD,$(depfile) -I$(srctree)/include/uapi $< | $(AS68K) -m68360 -o $(obj)…
/Linux-v4.19/drivers/iio/pressure/
Dbmp280-core.c42 enum { AC1, AC2, AC3, AC4, AC5, AC6, B1, B2, MB, MC, MD }; enumerator
55 s16 MD; member
793 calib->MD = be16_to_cpu(buf[MD]); in bmp180_read_calib()
810 x2 = (calib->MC << 11) / (x1 + calib->MD); in bmp180_compensate_temp()
/Linux-v4.19/tools/build/feature/
DMakefile72 __BUILD = $(CC) $(CFLAGS) -MD -Wall -Werror -o $@ $(patsubst %.bin,%.c,$(@F)) $(LDFLAGS)
75 __BUILDXX = $(CXX) $(CXXFLAGS) -MD -Wall -Werror -o $@ $(patsubst %.bin,%.cpp,$(@F)) $(LDFLAGS)
/Linux-v4.19/arch/powerpc/boot/
DMakefile205 cmd_bootcc = $(BOOTCC) -Wp,-MD,$(depfile) $(BOOTCFLAGS) -c -o $@ $<
208 cmd_bootas = $(BOOTCC) -Wp,-MD,$(depfile) $(BOOTAFLAGS) -c -o $@ $<
/Linux-v4.19/Documentation/
Dldm.txt25 Once the LDM driver has divided up the disk, you can use the MD driver to
/Linux-v4.19/tools/build/Documentation/
DBuild.txt154 - Dependency rules generated by 'gcc -Wp,-MD,...'
/Linux-v4.19/arch/sh/kernel/cpu/sh3/
Dentry.S332 shll k0 ! Check MD bit (bit30) by shifting it into...
/Linux-v4.19/drivers/net/fddi/skfp/h/
Dsupern_2.h41 #define MD 0xffffffff macro

12