| /linux-5.19.10/Documentation/filesystems/ |
| D | sysv-fs.rst | 8 - Xenix FS,
9 - SystemV/386 FS,
10 - Coherent FS.
30 - Coherent FS:
36 - SystemV Release 2 FS:
40 for this FS on hard disk yet.
43 These filesystems are rather similar. Here is a comparison with Minix FS:
47 - Minix FS 0x81 Linux/Minix
48 - Xenix FS ??
49 - SystemV FS ??
[all …]
|
| D | coda.rst | 152 assists in locating the correct FS drivers. Sometimes after extensive
153 pre-processing, the VFS starts invoking exported routines in the FS
154 driver. This is the point where the FS specific processing of the
158 The FS layer for Coda must expose and implement several interfaces.
160 the Coda FS layer, so the Coda FS driver must expose the VFS interface
163 read/write and create and remove objects. The Coda FS layer services
166 come back to the FS driver, servicing of the VFS call continues and
170 As a result of this design a basic interface exposed by the FS driver
177 **Interfaces of the Coda FS Driver**
179 Furthermore the FS layer provides for a special path of communication
[all …]
|
| /linux-5.19.10/tools/lib/api/fs/ |
| D | fs.h | 16 #define FS(name) \ macro
33 FS(sysfs)
34 FS(procfs)
35 FS(debugfs)
36 FS(tracefs)
37 FS(hugetlbfs)
38 FS(bpf_fs)
40 #undef FS
|
| D | fs.c | 297 #define FS(name, idx) \ macro
313 FS(sysfs, FS__SYSFS);
314 FS(procfs, FS__PROCFS);
315 FS(debugfs, FS__DEBUGFS);
316 FS(tracefs, FS__TRACEFS);
317 FS(hugetlbfs, FS__HUGETLBFS);
318 FS(bpf_fs, FS__BPF_FS);
|
| /linux-5.19.10/Documentation/x86/x86_64/ |
| D | fsgs.rst | 3 Using FS and GS segments in user space applications
22 always 0 to provide a full 64bit address space. The FS and GS segments are
25 Common FS and GS usage
28 The FS segment is commonly used to address Thread Local Storage (TLS). FS
31 thread and the compiler emits the FS: address prefix for accesses to these
32 variables. Each thread has its own FS base address so common code can be
34 instances. Applications should not use FS for other purposes when they use
35 runtimes or threading libraries which manage the per thread FS.
41 Reading and writing the FS/GS base address
44 There exist two mechanisms to read and write the FS/GS base address:
[all …]
|
| /linux-5.19.10/tools/testing/selftests/rcutorture/formal/srcu-cbmc/ |
| D | modify_srcu.awk | 22 FS="([ \\\\\t\n\v\f;,.=(){}+*/<>&|^-]|\\[|\\]|" comment_regexp "|" quote_regexp ")+";
142 if (match($0, FS) > 0) {
171 if (match($0, "^(" FS ")+") > 0) {
191 $0 ~ "^struct(" FS ")+srcu_struct(" FS ")+\\{") {
245 match(old_record, "^"name"("FS")+=");
316 $0 ~ "^struct(" FS ")+rcu_synchronize(" FS ")+\\{") {
|
| /linux-5.19.10/Documentation/translations/zh_CN/core-api/ |
| D | gfp_mask-from-fs-io.rst | 16 从FS/IO上下文中使用的GFP掩码
25 文件系统和IO栈中的代码路径在分配内存时必须小心，以防止因直接调用FS或IO路径的内
42 没有内存分配可以追溯到FS/IO中。
49 然后，FS/IO代码在任何与回收有关的关键部分开始之前简单地调用适当的保存函数
|
| /linux-5.19.10/Documentation/filesystems/caching/ |
| D | fscache.rst | 13 FS-Cache mediates between cache backends (such as CacheFiles) and network
24 | AFS |----->| | | FS-Cache |
34 Or to look at it another way, FS-Cache is a module that provides a caching
50 | NFS |----->| FS-Cache |
71 FS-Cache does not follow the idea of completely loading every netfs file
91 FS-Cache provides the following facilities:
145 The netfs API to FS-Cache can be found in:
149 The cache backend API to FS-Cache can be found in:
157 If FS-Cache is compiled with the following options enabled::
165 This shows counts of a number of events that can happen in FS-Cache:
[all …]
|
| /linux-5.19.10/drivers/net/ethernet/freescale/fs_enet/ |
| D | mac-fec.c | 68 #define FS(_fecp, _reg, _v) FW(_fecp, _reg, FR(_fecp, _reg) | (_v)) macro
166 FS(fecp, r_cntrl, FEC_RCNTRL_PROM); in set_promiscuous_mode()
287 FS(fecp, dma_control, 0xC0000000); in restart()
310 FS(fecp, r_cntrl, fpi->use_rmii ? in restart()
318 FS(fecp, x_cntrl, FEC_TCNTRL_FDEN); /* FD enable */ in restart()
320 FS(fecp, r_cntrl, FEC_RCNTRL_DRT); in restart()
370 FS(fecp, r_cntrl, fpi->use_rmii ? in stop()
373 FS(fecp, ecntrl, FEC_ECNTRL_PINMUX | FEC_ECNTRL_ETHER_EN); in stop()
392 FS(fecp, imask, FEC_NAPI_EVENT_MSK); in napi_enable_fs()
|
| /linux-5.19.10/arch/x86/kernel/ |
| D | process_64.c | 150 FS, enumerator
242 if (which == FS) in save_base_legacy()
262 save_base_legacy(task, task->thread.fsindex, FS); in save_fsgs()
287 if (which == FS) in loadseg()
331 wrmsrl(which == FS ? MSR_FS_BASE : MSR_KERNEL_GS_BASE, in load_seg_legacy()
372 loadseg(FS, next->fsindex); in x86_fsgsbase_load()
381 next->fsindex, next->fsbase, FS); in x86_fsgsbase_load()
792 loadseg(FS, 0); in do_arch_prctl_64()
|
| /linux-5.19.10/tools/perf/arch/x86/tests/ |
| D | regs_load.S | 18 #define FS 14 * 8 macro
51 movq $0, FS(%rdi)
88 movl $0, FS(%edi)
|
| /linux-5.19.10/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 4 GFP masks used from FS/IO context
15 memory reclaim calling back into the FS or IO paths and blocking on
36 mask so no memory allocation can recurse back in the FS/IO.
43 FS/IO code then simply calls the appropriate save function before
|
| /linux-5.19.10/arch/x86/um/ |
| D | ptrace_64.c | 48 [FS >> 3] = HOST_FS,
81 case FS: in putreg()
157 case FS: in getreg()
|
| D | user-offsets.c | 36 DEFINE(HOST_FS, FS); in foo()
66 DEFINE_LONGS(HOST_FS, FS); in foo()
|
| D | ptrace_32.c | 66 [FS] = HOST_FS,
94 case FS: in putreg()
150 case FS: in getreg()
|
| /linux-5.19.10/fs/verity/ |
| D | Kconfig | 4 bool "FS Verity (read-only file-based authenticity protection)"
38 bool "FS Verity debugging"
46 bool "FS Verity builtin signature support"
|
| /linux-5.19.10/Documentation/devicetree/bindings/phy/ |
| D | phy-stm32-usbphyc.yaml | 85 # all optional parameters to tune the interface of the PHY (HS for High-Speed, FS for Full-
93 description: Disables the LS/FS feedback capacitor
113 description: Enables the FS rise/fall tuning option
189 description: Disables the short circuit protection in LS/FS driver
|
| /linux-5.19.10/Documentation/devicetree/bindings/sound/ |
| D | fsl,esai.txt | 31 derive HCK, SCK and FS.
33 derive HCK, SCK and FS.
|
| D | realtek,rt1015p.yaml | 14 only supports S24, 48kHz, 64FS.
|
| /linux-5.19.10/arch/x86/include/uapi/asm/ |
| D | ptrace-abi.h | 16 #define FS 9 macro
|
| /linux-5.19.10/tools/testing/selftests/x86/ |
| D | fsgsbase.c | 117 enum which_base { FS, GS }; enumerator
130 if (which == FS) { in read_base()
146 if (which == FS) { in read_base()
|
| /linux-5.19.10/Documentation/filesystems/ext4/ |
| D | group_descr.rst | 36 checksum is the crc16 of the FS UUID, the group number, and the group
38 checksum is the lower 16 bits of the checksum of the FS UUID, the group
40 checksums are calculated against the FS UUID, the group number, and the
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | init.rst | 9 1) **Unable to mount root FS**: Set "debug" kernel parameter (in bootloader
13 root FS type (and ``root=`` kernel parameter points to the correct
|
| /linux-5.19.10/fs/omfs/ |
| D | Kconfig | 9 more efficient than a standard FS for MPEG files, in fact likely
|
| /linux-5.19.10/Documentation/translations/zh_CN/admin-guide/ |
| D | init.rst | 21 1) **无法挂载根文件系统Unable to mount root FS** ：请设置“debug”内核参数（在
|