| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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);
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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 ")+\\{") {
|
| /kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
| D | backend-api.rst | 4 FS-Cache Cache backend API
7 The FS-Cache system provides an API by which actual caches can be supplied to
8 FS-Cache for it to then serve out to network filesystems and other interested
39 The cache should then be registered with FS-Cache by passing a pointer to the
48 * "fsdef" which should point to the object representation for the FS-Cache
50 here. FS-Cache keeps the caller's reference to the index object if
81 (2) that of one of the processes in the FS-Cache thread pool.
88 This is left to the cache to handle; FS-Cache makes no effort in this regard.
94 The cache may present data to the outside world through FS-Cache's interfaces
105 * Index/Data file FS-Cache representation cookie::
[all …]
|
| D | fscache.rst | 13 FS-Cache mediates between cache backends (such as CacheFS) 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:
120 (8) Cookies can be "retired" upon release. At this point FS-Cache will mark
131 FS-Cache maintains a virtual indexing tree in which all indices, files, objects
176 The very top index is the FS-Cache master index in which individual netfs's
184 The netfs API to FS-Cache can be found in:
[all …]
|
| D | object.rst | 26 FS-Cache maintains an in-kernel representation of each object that a netfs is
30 FS-Cache also maintains a separate in-kernel representation of the objects that
96 Within FS-Cache, each active object is managed by its own individual state
174 FS-Cache expects the cache backend to probe the cache to see whether this
182 At the completion of lookup, FS-Cache will let the netfs go ahead with
194 FS-Cache expects the cache to create
199 At the completion of creation, FS-Cache will start processing write
|
| D | netfs-api.rst | 4 FS-Cache Network Filesystem API
7 There's an API by which a network filesystem can make use of the FS-Cache
12 FS-Cache to make finding objects faster and to make retiring of groups of
43 (18) FS-Cache specific page flags.
49 FS-Cache needs a description of the network filesystem. This is specified
95 their index hierarchies in quite the same way, FS-Cache tries to impose as few
152 This defines an index, which is a special FS-Cache type.
231 This is called by FS-Cache to indicate that a backing store is being
266 FS-Cache permits the use of more than one cache. To permit particular index
269 FS-Cache as to which cache should be used. The problem with doing that is that
[all …]
|
| /kernel/linux/linux-5.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()
|
| /kernel/linux/linux-5.10/arch/x86/kernel/ |
| D | process_64.c | 149 FS, enumerator
241 if (which == FS) in save_base_legacy()
261 save_base_legacy(task, task->thread.fsindex, FS); in save_fsgs()
286 if (which == FS) in loadseg()
330 wrmsrl(which == FS ? MSR_FS_BASE : MSR_KERNEL_GS_BASE, in load_seg_legacy()
348 loadseg(FS, next->fsindex); in x86_fsgsbase_load()
357 next->fsindex, next->fsbase, FS); in x86_fsgsbase_load()
769 loadseg(FS, 0); in do_arch_prctl_64()
|
| /kernel/linux/linux-5.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)
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.10/fs/verity/ |
| D | Kconfig | 4 bool "FS Verity (read-only file-based authenticity protection)"
33 bool "FS Verity debugging"
41 bool "FS Verity builtin signature support"
|
| /kernel/linux/linux-5.10/arch/x86/um/ |
| D | ptrace_64.c | 47 [FS >> 3] = HOST_FS,
80 case FS: in putreg()
156 case FS: in getreg()
|
| D | user-offsets.c | 37 DEFINE(HOST_FS, FS); in foo()
67 DEFINE_LONGS(HOST_FS, FS); in foo()
|
| D | ptrace_32.c | 65 [FS] = HOST_FS,
93 case FS: in putreg()
149 case FS: in getreg()
|
| /kernel/liteos_m/components/fs/littlefs/ |
| D | Kconfig | 31 bool "Enable Little FS"
36 Answer Y to enable LiteOS support Little FS filesystem.
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | cleancache.rst | 239 - The FS should be block-device-based (e.g. a ram-based FS such
241 - To ensure coherency/correctness, the FS must ensure that all
246 FS must provide an "encode_fh" function.
247 - The FS must call the VFS superblock alloc and deactivate routines
249 - To maximize performance, all pages fetched from the FS should
250 go through the do_mpag_readpage routine or the FS should add
252 - Currently, the FS blocksize must be the same as PAGESIZE. This
255 - A clustered FS should invoke the "shared_init_fs" cleancache
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | fsl,esai.txt | 31 derive HCK, SCK and FS.
33 derive HCK, SCK and FS.
|
| /kernel/linux/linux-5.10/arch/x86/include/uapi/asm/ |
| D | ptrace-abi.h | 16 #define FS 9 macro
|
| /kernel/linux/patches/linux-5.10/prebuilts/usr/include/asm-x86/asm/ |
| D | ptrace-abi.h | 31 #define FS 9 macro
|
| /kernel/linux/linux-5.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()
|
| /kernel/linux/linux-5.10/arch/arm/mm/ |
| D | abort-ev7.S | 41 bic r1, r1, #0xf @ Fix up FSR FS[5:0]
|