| /linux-2.6.39/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 | btrfs.txt | 33 * Efficient incremental backup and FS mirroring (not yet implemented)
87 btrfsck: do a limited check of the FS extent trees.
89 btrfs-debug-tree: print all of the FS metadata in text form. Example:
|
| 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 …]
|
| D | omfs.txt | 12 Note, it is not recommended that this FS be used in place of a general
52 __be64 h_self; /* FS block where this is located */
|
| /linux-2.6.39/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 | 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
39 (16) FS-Cache specific page flags.
46 FS-Cache needs a description of the network filesystem. This is specified
93 their index hierarchies in quite the same way, FS-Cache tries to impose as few
164 This defines an index, which is a special FS-Cache type.
266 This is called by FS-Cache to indicate that a backing store is being
303 FS-Cache permits the use of more than one cache. To permit particular index
306 FS-Cache as to which cache should be used. The problem with doing that is that
[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 | operations.txt | 24 FS-Cache has an asynchronous operations handling facility that it uses for its
30 and FS-Cache will create operations and pass them off to the appropriate cache
113 This is, for example, used by FS-Cache to handle background writes of
|
| /linux-2.6.39/drivers/net/fs_enet/ |
| D | mac-fec.c | 73 #define FS(_fecp, _reg, _v) FW(_fecp, _reg, FR(_fecp, _reg) | (_v)) macro
173 FS(fecp, r_cntrl, FEC_RCNTRL_PROM); in set_promiscuous_mode()
305 FS(fecp, dma_control, 0xC0000000); in restart()
328 FS(fecp, r_cntrl, FEC_RCNTRL_MII_MODE); in restart()
335 FS(fecp, x_cntrl, FEC_TCNTRL_FDEN); /* FD enable */ in restart()
337 FS(fecp, r_cntrl, FEC_RCNTRL_DRT); in restart()
384 FS(fecp, r_cntrl, FEC_RCNTRL_MII_MODE); /* MII enable */ in stop()
385 FS(fecp, ecntrl, FEC_ECNTRL_PINMUX | FEC_ECNTRL_ETHER_EN); in stop()
404 FS(fecp, imask, FEC_NAPI_RX_EVENT_MSK); in napi_enable_rx()
|
| /linux-2.6.39/Documentation/hwmon/ |
| D | ads1015 | 65 In this case only in2_input (FS +/- 4.096 V, 128 SPS) and in4_input
66 (FS +/- 0.512 V, 2400 SPS) would be created.
|
| /linux-2.6.39/arch/um/sys-x86_64/ |
| D | ptrace.c | 34 case FS: in putreg()
85 case FS: in getreg()
|
| D | user-offsets.c | 47 DEFINE_LONGS(HOST_FS, FS); in foo()
|
| /linux-2.6.39/arch/um/sys-i386/ |
| D | ptrace.c | 57 case FS: in putreg()
113 case FS: in getreg()
|
| D | user-offsets.c | 40 DEFINE(HOST_FS, FS); in foo()
|
| /linux-2.6.39/arch/arm/mach-ns9xxx/ |
| D | processor-ns9360.c | 33 >> REGGETIM(pll, SYS_PLL, FS); in ns9360_systemclock()
|
| /linux-2.6.39/arch/x86/include/asm/ |
| D | ptrace-abi.h | 15 #define FS 9 macro
|
| /linux-2.6.39/arch/um/sys-x86_64/shared/sysdep/ |
| D | ptrace.h | 59 #define FS (HOST_FS * sizeof(long)) macro
178 case FS : val = UPT_FS (regs); break; \
216 case FS: UPT_FS(regs) = __upt_val; break; \
|
| /linux-2.6.39/arch/arm/mm/ |
| D | abort-ev7.S | 48 bic r1, r1, #0xf @ Fix up FSR FS[5:0]
|
| /linux-2.6.39/fs/fuse/ |
| D | Kconfig | 14 If you want to develop a userspace FS, or if you want to use
|
| /linux-2.6.39/fs/omfs/ |
| D | Kconfig | 8 more efficient than a standard FS for MPEG files, in fact likely
|
| /linux-2.6.39/arch/um/sys-i386/shared/sysdep/ |
| D | ptrace.h | 121 case FS: val = UPT_FS(regs); break; \
148 case FS: UPT_FS(regs) = val; break; \
|
| /linux-2.6.39/Documentation/ |
| D | init.txt | 8 A) Unable to mount root FS
17 A) make sure you have the correct root FS type
|
| /linux-2.6.39/fs/9p/ |
| D | Kconfig | 20 caching support for 9p clients using FS-Cache
|
| /linux-2.6.39/arch/cris/arch-v32/drivers/ |
| D | Kconfig | 9 This option enables the ETRAX FS built-in 10/100Mbit Ethernet
87 Enables the ETRAX FS serial driver for ser0 (ttyS0)
107 Enables the ETRAX FS serial driver for ser0 (ttyS0)
157 Enables the ETRAX FS serial driver for ser1 (ttyS1).
204 Enables the ETRAX FS serial driver for ser2 (ttyS2).
252 Enables the ETRAX FS serial driver for ser3 (ttyS3).
299 Enables the ETRAX FS serial driver for ser4 (ttyS4).
371 Enables the ETRAX FS synchronous serial driver.
687 SPI master controller on Axis ETRAX FS and later. The
696 on Axis ETRAX FS and later. The driver can be configured to
|