| /kernel/linux/linux-5.10/drivers/scsi/aic94xx/ |
| D | aic94xx_dump.c | 24 #define MD(x) (1 << (x)) macro
34 {"LmMnSCBPTR", 0x20, 16, MD(0)|MD(1)|MD(2)|MD(3)|MD(4) },
35 {"LmMnDDBPTR", 0x22, 16, MD(0)|MD(1)|MD(2)|MD(3)|MD(4) },
43 {"LmMnDMAERRS", 0x46, 8, MD(0)|MD(1) },
44 {"LmMnSGDMAERRS", 0x47, 8, MD(0)|MD(1) },
45 {"LmMnEXPHDRP", 0x48, 8, MD(0) },
46 {"LmMnSASAALIGN", 0x48, 8, MD(1) },
47 {"LmMnMSKHDRP", 0x49, 8, MD(0) },
48 {"LmMnSTPALIGN", 0x49, 8, MD(1) },
49 {"LmMnRCVHDRP", 0x4A, 8, MD(0) },
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/md/ |
| D | raid5-cache.rst | 29 unclean shutdown. We call an array degraded if it has inconsistent data. MD
36 two-step write will guarantee MD can recover correct data after unclean
39 In write-through mode, MD reports IO completion to upper layer (usually
53 write. For non-full-stripe writes, MD must read old data before the new parity
61 In write-back mode, MD reports IO completion to upper layer (usually
66 In write-back mode, MD also caches data in memory. The memory cache includes
85 checksum is an optimization because MD can write meta and data freely without
86 worry about the order. MD superblock has a field pointed to the valid meta data
90 order in which MD writes data to cache disk and RAID disks. Specifically, in
91 write-through mode, MD calculates parity for IO data, writes both IO data and
[all …]
|
| D | md-cluster.rst | 2 MD Cluster
5 The cluster MD is a shared-device RAID for a cluster, it supports
383 There are somethings which are not supported by cluster MD yet.
|
| /kernel/linux/linux-5.10/arch/um/scripts/ |
| D | Makefile.rules | 12 …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)
|
| /kernel/linux/linux-5.10/tools/build/ |
| D | Build.include | 26 # The temporary file to save gcc -MD generated dependencies must not
94 c_flags_1 = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(CFLAGS) -D"BUILD_STR(s)=\#s" $(CFLAGS_$(basetarget).o) …
97 cxx_flags = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(CXXFLAGS) -D"BUILD_STR(s)=\#s" $(CXXFLAGS_$(basetarget)…
102 host_c_flags = -Wp,-MD,$(depfile) -Wp,-MT,$@ $(KBUILD_HOSTCFLAGS) -D"BUILD_STR(s)=\#s" $(HOSTCFLAGS…
|
| /kernel/linux/linux-5.10/arch/sh/kernel/cpu/sh2a/ |
| D | entry.S | 46 bld.b #6,@(0,r2) !previus SR.MD
47 bst.b #6,@(4*4,r15) !set cpu mode to SR.MD
50 bset.b #6,@(0,r2) !set SR.MD
212 shlr2 r1 ! clear MD bit
238 ! bit30 = MD (compatible SH3/4)
|
| /kernel/linux/linux-5.10/arch/arm64/kernel/vdso32/ |
| D | Makefile | 182 cmd_vdsocc = $(CC_COMPAT) -Wp,-MD,$(depfile) $(VDSO_CFLAGS) -c -o $@ $<
184 …cmd_vdsocc_gettimeofday = $(CC_COMPAT) -Wp,-MD,$(depfile) $(VDSO_CFLAGS) $(VDSO_CFLAGS_gettimeofda…
186 cmd_vdsoas = $(CC_COMPAT) -Wp,-MD,$(depfile) $(VDSO_AFLAGS) -c -o $@ $<
|
| /kernel/linux/linux-5.10/net/nsh/ |
| D | Kconfig | 8 only MD type 1 and only with the openvswitch module.
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | ntfs.rst | 17 - The Software RAID / MD driver
18 - Limitations when using the MD driver
36 use the kernel's Software RAID / MD driver. See section "Using Software RAID
249 Device-Mapper driver or the kernel's Software RAID / MD driver. The former is
266 Software RAID / MD driver for raid level 5, see the next section for details.
390 The Software RAID / MD driver
394 Software RAID / MD driver. For which you need to set up your /etc/raidtab
399 the MD driver with NTFS volumes" especially if you want to use linear raid).
405 superblock used by the MD driver would damage the NTFS volume.
428 Note for stripe sets with parity you will also need to tell the MD driver
[all …]
|
| /kernel/linux/linux-5.10/arch/sh/kernel/cpu/sh2/ |
| D | entry.S | 56 or r0,r3 ! set MD
289 and r1,r3 ! copy MD bit
291 shll2 r1 ! clear MD bit
352 ! bit30 = MD (compatible SH3/4)
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | dm-raid.rst | 5 The device-mapper RAID (dm-raid) target provides a bridge from DM to MD.
6 It allows the MD RAID drivers to be accessed using a device-mapper
192 MD personalities supporting such device addition will read the data from
222 1.9.0 supports up to 253 which is enforced by the used MD kernel runtime.
394 1.7.0 Add support for MD RAID0 mappings.
411 1.12.1 Fix for MD deadlock between mddev_suspend() and md_write_start() available
420 1.15.0 Fix size extensions not being synchronized in case of new MD bitmap
|
| /kernel/linux/linux-5.10/drivers/mfd/ |
| D | ssbi.c | 42 #define SET_SSBI_MODE2_REG_ADDR_15_8(MD, AD) \ argument
43 (((MD) & 0x0F) | ((((AD) >> 8) << SSBI_MODE2_REG_ADDR_15_8_SHFT) & \
|
| /kernel/linux/linux-5.10/arch/sh/kernel/ |
| D | head_32.S | 59 mov.l 1f, r0 ! MD=1, RB=0, BL=0, IMASK=0xF
340 1: .long 0x500080F0 ! MD=1, RB=0, BL=1, FD=1, IMASK=0xF
|
| /kernel/liteos_a/tools/build/mk/ |
| D | module.mk | 44 LOCAL_FLAGS += -MD -MP
|
| /kernel/linux/linux-5.10/drivers/md/ |
| D | Kconfig | 6 menuconfig MD config
14 if MD
89 an error free MD (multiple device) to the higher levels of the
165 the MD framework. It is not under active development. New
172 tristate "Faulty test module for MD"
182 tristate "Cluster Support for MD"
187 Clustering support for MD devices. This enables locking and
189 nodes in the cluster can access the MD devices simultaneously.
622 endif # MD
|
| /kernel/linux/linux-5.10/samples/bpf/ |
| D | Makefile.target | 50 tprogc_flags = -Wp,-MD,$(depfile) $(_tprogc_flags)
|
| /kernel/linux/linux-5.10/arch/x86/um/ |
| D | Makefile | 38 $(obj)/user-offsets.s: c_flags = -Wp,-MD,$(depfile) $(USER_CFLAGS) \
|
| /kernel/linux/linux-5.10/drivers/iio/pressure/ |
| D | bmp280-core.c | 39 enum { AC1, AC2, AC3, AC4, AC5, AC6, B1, B2, MB, MC, MD }; enumerator
52 s16 MD; member
783 calib->MD = be16_to_cpu(buf[MD]); in bmp180_read_calib()
800 x2 = (calib->MC << 11) / (x1 + calib->MD); in bmp180_compensate_temp()
|
| /kernel/linux/linux-5.10/arch/s390/purgatory/ |
| D | Makefile | 26 KBUILD_CFLAGS += -c -MD -Os -m64 -msoft-float -fno-common
|
| /kernel/linux/linux-5.10/drivers/net/wan/ |
| D | Makefile | 64 … cmd_m68kas_o_S = $(M68KCC) -D__ASSEMBLY__ -Wp,-MD,$(depfile) -I$(srctree)/include/uapi -c -o $@ $<
|
| /kernel/linux/linux-5.10/tools/build/feature/ |
| D | Makefile | 83 __BUILD = $(CC) $(CFLAGS) -MD -Wall -Werror -o $@ $(patsubst %.bin,%.c,$(@F)) $(LDFLAGS)
86 __BUILDXX = $(CXX) $(CXXFLAGS) -MD -Wall -Werror -o $@ $(patsubst %.bin,%.cpp,$(@F)) $(LDFLAGS)
|
| /kernel/linux/linux-5.10/arch/powerpc/boot/ |
| D | Makefile | 203 cmd_bootcc = $(BOOTCC) -Wp,-MD,$(depfile) $(BOOTCFLAGS) -c -o $@ $<
206 cmd_bootas = $(BOOTCC) -Wp,-MD,$(depfile) $(BOOTAFLAGS) -c -o $@ $<
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | ldm.rst | 25 Once the LDM driver has divided up the disk, you can use the MD driver to
|
| /kernel/linux/linux-5.10/tools/build/Documentation/ |
| D | Build.txt | 154 - Dependency rules generated by 'gcc -Wp,-MD,...'
|
| /kernel/linux/linux-5.10/arch/sh/kernel/cpu/sh3/ |
| D | entry.S | 329 shll k0 ! Check MD bit (bit30) by shifting it into...
|