| /Linux-v4.19/Documentation/filesystems/ |
| D | sysv-fs.txt | 2 - Xenix FS,
3 - SystemV/386 FS,
4 - Coherent FS.
18 - Coherent FS:
22 - SystemV Release 2 FS:
25 for this FS on hard disk yet.
28 These filesystems are rather similar. Here is a comparison with Minix FS:
31 - Minix FS 0x81 Linux/Minix
32 - Xenix FS ??
33 - SystemV FS ??
[all …]
|
| D | coda.txt | 208 assists in locating the correct FS drivers. Sometimes after extensive
209 pre-processing, the VFS starts invoking exported routines in the FS
210 driver. This is the point where the FS specific processing of the
214 The FS layer for Coda must expose and implement several interfaces.
216 the Coda FS layer, so the Coda FS driver must expose the VFS interface
219 read/write and create and remove objects. The Coda FS layer services
222 come back to the FS driver, servicing of the VFS call continues and
226 As a result of this design a basic interface exposed by the FS driver
238 Interfaces of the Coda FS Driver
240 Furthermore the FS layer provides for a special path of communication
[all …]
|
| /Linux-v4.19/tools/lib/api/fs/ |
| D | fs.h | 16 #define FS(name) \ macro
21 FS(sysfs)
22 FS(procfs)
23 FS(debugfs)
24 FS(tracefs)
25 FS(hugetlbfs)
26 FS(bpf_fs)
28 #undef FS
|
| D | fs.c | 278 #define FS(name, idx) \ macro
294 FS(sysfs, FS__SYSFS);
295 FS(procfs, FS__PROCFS);
296 FS(debugfs, FS__DEBUGFS);
297 FS(tracefs, FS__TRACEFS);
298 FS(hugetlbfs, FS__HUGETLBFS);
299 FS(bpf_fs, FS__BPF_FS);
|
| /Linux-v4.19/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-v4.19/Documentation/filesystems/caching/ |
| D | backend-api.txt | 2 FS-CACHE CACHE BACKEND API
5 The FS-Cache system provides an API by which actual caches can be supplied to
6 FS-Cache for it to then serve out to network filesystems and other interested
38 The cache should then be registered with FS-Cache by passing a pointer to the
47 (*) "fsdef" which should point to the object representation for the FS-Cache
49 here. FS-Cache keeps the caller's reference to the index object if
82 (2) that of one of the processes in the FS-Cache thread pool.
89 This is left to the cache to handle; FS-Cache makes no effort in this regard.
96 The cache may present data to the outside world through FS-Cache's interfaces
108 (*) Index/Data file FS-Cache representation cookie:
[all …]
|
| D | fscache.txt | 12 FS-Cache mediates between cache backends (such as CacheFS) and network
23 | AFS |----->| FS-Cache |
33 Or to look at it another way, FS-Cache is a module that provides a caching
49 | NFS |----->| FS-Cache |
70 FS-Cache does not follow the idea of completely loading every netfs file
90 FS-Cache provides the following facilities:
119 (8) Cookies can be "retired" upon release. At this point FS-Cache will mark
130 FS-Cache maintains a virtual indexing tree in which all indices, files, objects
175 The very top index is the FS-Cache master index in which individual netfs's
183 The netfs API to FS-Cache can be found in:
[all …]
|
| D | object.txt | 25 FS-Cache maintains an in-kernel representation of each object that a netfs is
29 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
175 FS-Cache expects the cache backend to probe the cache to see whether this
183 At the completion of lookup, FS-Cache will let the netfs go ahead with
195 FS-Cache expects the cache to create
200 At the completion of creation, FS-Cache will start processing write
|
| D | netfs-api.txt | 2 FS-CACHE NETWORK FILESYSTEM API
5 There's an API by which a network filesystem can make use of the FS-Cache
10 FS-Cache to make finding objects faster and to make retiring of groups of
41 (18) FS-Cache specific page flags.
48 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
154 This defines an index, which is a special FS-Cache type.
230 This is called by FS-Cache to indicate that a backing store is being
267 FS-Cache permits the use of more than one cache. To permit particular index
270 FS-Cache as to which cache should be used. The problem with doing that is that
[all …]
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 2 GFP masks used from FS/IO context
13 memory reclaim calling back into the FS or IO paths and blocking on
34 mask so no memory allocation can recurse back in the FS/IO.
41 FS/IO code then simply calls the appropriate save function before
|
| /Linux-v4.19/arch/x86/kernel/ |
| D | process_64.c | 159 FS, enumerator
201 if (which == FS) in save_base_legacy()
212 save_base_legacy(task, task->thread.fsindex, FS); in save_fsgs()
233 if (which == FS) in loadseg()
277 wrmsrl(which == FS ? MSR_FS_BASE : MSR_KERNEL_GS_BASE, in load_seg_legacy()
477 next->fsindex, next->fsbase, FS); in __switch_to()
|
| /Linux-v4.19/arch/x86/um/ |
| D | ptrace_64.c | 47 [FS >> 3] = HOST_FS,
88 case FS: in putreg()
167 case FS: in getreg()
|
| D | ptrace_32.c | 65 [FS] = HOST_FS,
93 case FS: in putreg()
149 case FS: in getreg()
|
| D | user-offsets.c | 49 DEFINE(HOST_FS, FS); in foo()
79 DEFINE_LONGS(HOST_FS, FS); in foo()
|
| /Linux-v4.19/tools/testing/selftests/x86/ |
| D | fsgsbase.c | 74 enum which_base { FS, GS }; enumerator
87 if (which == FS) { in read_base()
103 if (which == FS) { in read_base()
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | ads1015 | 69 In this case only in2_input (FS +/- 4.096 V, 128 SPS) and in4_input
70 (FS +/- 0.512 V, 2400 SPS) would be created.
|
| /Linux-v4.19/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
|
| /Linux-v4.19/Documentation/devicetree/bindings/sound/ |
| D | fsl,esai.txt | 27 derive HCK, SCK and FS.
29 derive HCK, SCK and FS.
|
| /Linux-v4.19/fs/crypto/ |
| D | Kconfig | 2 tristate "FS Encryption (Per-file encryption)"
|
| /Linux-v4.19/arch/x86/include/uapi/asm/ |
| D | ptrace-abi.h | 16 #define FS 9 macro
|
| /Linux-v4.19/Documentation/devicetree/bindings/usb/ |
| D | dwc2.txt | 18 - "st,stm32f4x9-fsotg": The DWC2 USB FS/HS controller instance in STM32F4x9 SoCs
19 configured in FS mode;
|
| /Linux-v4.19/arch/arm/mm/ |
| D | abort-ev7.S | 41 bic r1, r1, #0xf @ Fix up FSR FS[5:0]
|
| /Linux-v4.19/fs/omfs/ |
| D | Kconfig | 8 more efficient than a standard FS for MPEG files, in fact likely
|
