Home
last modified time | relevance | path

Searched refs:be (Results 1 – 25 of 73) sorted by relevance

123

/fs/nfs/blocklayout/
Dextents.c276 static void print_short_extent(struct pnfs_block_short_extent *be) in print_short_extent() argument
278 dprintk("PRINT SHORT EXTENT extent %p\n", be); in print_short_extent()
279 if (be) { in print_short_extent()
280 dprintk(" be_f_offset %llu\n", (u64)be->bse_f_offset); in print_short_extent()
281 dprintk(" be_length %llu\n", (u64)be->bse_length); in print_short_extent()
287 struct pnfs_block_short_extent *be; in print_clist() local
293 list_for_each_entry(be, list, bse_node) { in print_clist()
295 print_short_extent(be); in print_clist()
375 int bl_mark_for_commit(struct pnfs_block_extent *be, in bl_mark_for_commit() argument
380 struct pnfs_block_layout *bl = container_of(be->be_inval, in bl_mark_for_commit()
[all …]
Dblocklayoutdev.c222 static int verify_extent(struct pnfs_block_extent *be, in verify_extent() argument
226 if (be->be_state == PNFS_BLOCK_READWRITE_DATA || in verify_extent()
227 be->be_state == PNFS_BLOCK_INVALID_DATA) in verify_extent()
229 if (be->be_f_offset != lv->start) in verify_extent()
231 lv->start += be->be_length; in verify_extent()
235 if (be->be_state == PNFS_BLOCK_READWRITE_DATA) { in verify_extent()
236 if (be->be_f_offset != lv->start) in verify_extent()
240 lv->start += be->be_length; in verify_extent()
243 } else if (be->be_state == PNFS_BLOCK_INVALID_DATA) { in verify_extent()
244 if (be->be_f_offset != lv->start) in verify_extent()
[all …]
Dblocklayout.c70 static int is_hole(struct pnfs_block_extent *be, sector_t isect) in is_hole() argument
72 if (be->be_state == PNFS_BLOCK_NONE_DATA) in is_hole()
74 else if (be->be_state != PNFS_BLOCK_INVALID_DATA) in is_hole()
77 return !bl_is_sector_init(be->be_inval, isect); in is_hole()
83 static int is_writable(struct pnfs_block_extent *be, sector_t isect) in is_writable() argument
85 return (be->be_state == PNFS_BLOCK_READWRITE_DATA || in is_writable()
86 be->be_state == PNFS_BLOCK_INVALID_DATA); in is_writable()
145 struct pnfs_block_extent *be, in bl_alloc_init_bio() argument
159 bio->bi_sector = isect - be->be_f_offset + be->be_v_offset; in bl_alloc_init_bio()
160 bio->bi_bdev = be->be_mdev; in bl_alloc_init_bio()
[all …]
/fs/fscache/
DKconfig5 This option enables a generic filesystem caching manager that can be
7 Different sorts of caches can be plugged in, depending on the
16 This option causes statistical information to be gathered on local
23 multi-CPU system these may be on cachelines that keep bouncing
33 This option causes latency information to be gathered on local
40 and on a multi-CPU system these may be on cachelines that keep
41 bouncing between CPUs. On the other hand, the histogram may be
50 This permits debugging to be dynamically enabled in the local caching
51 management module. If this is set, the debugging output may be
60 Maintain a global list of active fscache objects that can be
/fs/pstore/
DKconfig7 be mounted as /dev/pstore. Only useful if you have
28 data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID].
39 ram buffer that can be decoded and dumped after reboot through
40 pstore filesystem. It can be used to determine what function
54 This enables panic and oops messages to be logged to a circular
55 buffer in RAM where it can be read back at some later point.
57 Note that for historical reasons, the module will be named
/fs/cifs/
DREADME39 6) make modules (or "make" if CIFS VFS not to be built as a module)
65 "net" may also be helpful since it may someday provide easier mount syntax for
70 domain to the proper network user. The mount.cifs mount helper can be
76 and maximum number of simultaneous requests to one server can be configured.
79 on kernel/fs/cifs/cifs.ko the list of configuration changes that can be made
80 at module initialization time (by running insmod cifs.ko) can be seen.
97 and execution of suid programs on the remote target would be enabled
98 by default. This can be changed, as with nfs and other filesystems,
100 though to be able to pass the suid flag to mount requires rebuilding
111 the utility umount.cifs may be used. It may be invoked directly, or if
[all …]
/fs/adfs/
DKconfig8 here, Linux will be able to read from ADFS partitions on hard drives
9 and from ADFS-formatted floppy discs. If you also want to be able to
12 The ADFS partition should be the first partition (i.e.,
16 To compile this code as a module, choose M here: the module will be
25 If you say Y here, you will be able to write to ADFS partitions on
/fs/xfs/
DKconfig19 module will be called xfs. Be aware, however, that if the file
28 If you say Y here, you will be able to set limits for disk usage on
33 filesystem to be migrated between Linux and IRIX without any need
36 If unsure, say N. More comprehensive documentation can be found in
37 README.quota in the xfsprogs package. XFS quota can be used either
58 If you say Y here you will be able to mount and use XFS filesystems
65 from all other requests, and this can be done quite transparently
78 conditions that occur that would otherwise be missed. It is much
93 Note that the resulting code will be HUGE and SLOW, and probably
/fs/cachefiles/
DKconfig17 This permits debugging to be dynamically enabled in the filesystem
18 caching on files module. If this is set, the debugging output may be
27 This option causes latency information to be gathered on CacheFiles
34 and on a multi-CPU system these may be on cachelines that keep
35 bouncing between CPUs. On the other hand, the histogram may be
/fs/fat/
DKconfig7 to include FAT support. You will then be able to mount partitions or
30 To compile this as a module, choose M here: the module will be called
33 -- they will have to be modules as well.
52 support" below), or you will not be able to see the long filenames
58 be called msdos.
74 To compile this as a module, choose M here: the module will be called
82 This option should be set to the codepage of your FAT filesystems.
83 It can be overridden with the "codepage" mount option.
93 that most of your FAT filesystems use, and can be overridden
/fs/romfs/
DKconfig6 initial ram disks of installation disks, but it could be used for
11 module will be called romfs. Note that the file system of your
12 root partition (the one containing the directory /) cannot be a
19 # Select the backing stores to be supported
26 Select the backing stores to be supported.
/fs/reiserfs/
DREADME9 Reiser, or authorized to be licensed by him, have been in the past,
10 and likely will be in the future, licensed to other parties under
12 want it to be owned by Hans Reiser, put your copyright label on that
18 It will be a kindness if you identify whether Hans Reiser is allowed
36 Finally, nothing in this license shall be interpreted to allow you to
59 utilities cannot be compiled without accessing the balancing code
61 you to specify where that code can be found.
64 recompile your kernel, most of the time. The errors you get will be
77 be the ones to compete against the entire internet by themselves. Be
89 writing the cleanest code. He always made the effort to be the best he
[all …]
/fs/cramfs/
DREADME25 The order of inode traversal is described as "width-first" (not to be
59 (For the last <block> of the file, the input may of course be smaller.)
60 Each <block> may be a different size. (See <block_pointer> above.)
88 compressed at a time. It's intended to be somewhere around
98 turn is defined as PAGE_SIZE (which can be as large as 32KB on arm).
99 This discrepancy is a bug, though it's not clear which should be
106 is that the generated cramfs cannot always be shared between different
148 must be no larger than 32KB) and discard what it doesn't need.
164 Given that cramfs will probably be used for CDs etc. as well as just
167 by filename, so the expansion doesn't even have to be a multiple of 4
DKconfig7 System). CramFs is designed to be a simple, small, and compressed
15 To compile this as a module, choose M here: the module will be called
17 directory /) cannot be compiled as a module.
/fs/nls/
DKconfig16 will be called nls_base.
45 codepage if you want to be able to read/write these filenames on
57 codepage if you want to be able to read/write these filenames on
69 codepage if you want to be able to read/write these filenames on
82 codepage if you want to be able to read/write these filenames on
98 codepage if you want to be able to read/write these filenames on
113 codepage if you want to be able to read/write these filenames on
124 codepage if you want to be able to read/write these filenames on
135 codepage if you want to be able to read/write these filenames on
146 codepage if you want to be able to read/write these filenames on
[all …]
/fs/jbd/
DKconfig5 currently used by the ext3 file system, but it could also be
12 To compile this device as a module, choose M here: the module will be
24 debugging output will be turned off.
26 If you select Y here, then you will be able to turn on debugging
/fs/jbd2/
DKconfig9 the ext4 and OCFS2 filesystems, but it could also be used to add
17 To compile this device as a module, choose M here. The module will be
29 By default, the debugging output will be turned off.
31 If you select Y here, then you will be able to turn on debugging
/fs/jffs2/
DLICENCE11 JFFS2 is distributed in the hope that it will be useful, but WITHOUT
23 files, these files do not by themselves cause the resulting work to be
25 these files must still be made available in accordance with section (3)
29 this file might be covered by the GNU General Public License.
DREADME.Locking11 be fairly close.
26 When writing new nodes, the alloc_sem must be held until the new nodes
83 to be called from bottom-half (timer) context (on the basis that nobody
108 has to be locked while walking the c->inocache_list hash buckets.
115 will not be removed. So, it is allowed to access it without locking
121 c->erase_completion has to be acquired first.
130 determine whether the 'deletion dirent' under consideration can be
133 erase_completion_lock cannot be held, so an alternative, more
138 Suggestions for alternative solutions to this problem would be welcomed.
163 Once xattr_sem released, there would be no assurance for the existence
/fs/ntfs/
DKconfig24 module will be called ntfs.
34 Y here. This will result in additional consistency checks to be
36 be written to the system log. Note that debugging messages are
59 renaming is possible. Note only non-resident files can be written to
61 be written to.
68 scratch of the NTFS support), it should be noted that the old NTFS
/fs/squashfs/
DKconfig16 archival use (i.e. in cases where a .tar.gz file may be used), and in
20 If you want to compile this as a module ( = code which can be
22 say M here. The module will be called squashfs. Note that the root
23 file system (the one containing the directory /) cannot be compiled
42 Only one block (data or metadata) can be decompressed at any
106 file systems will be readable without selecting this option.
121 file systems will be readable without selecting this option.
136 file systems will be readable without selecting this option.
181 Note there must be at least one cached fragment. Anything
/fs/nfs/
DKconfig11 will be called nfs.
14 install the user space mount.nfs command which can be found in
84 space programs which can be found in the Linux nfs-utils package,
128 may be sent in the NFS exchange_id operation. The value must be in
129 the format of a DNS domain name and should be set to the DNS domain
132 option should be set to the default "kernel.org".
149 Say Y here if you want NFS data to be cached locally on disc through
/fs/hpfs/
DKconfig7 partitions. Say Y if you want to be able to read files from and
10 option in order to be able to read them. Read
14 module will be called hpfs. If unsure, say N.
/fs/affs/
DKconfig7 if you want to be able to read and write files from and to an Amiga
8 FFS partition on your hard drive. Amiga floppies however cannot be
21 module will be called affs. If unsure, say N.
/fs/ncpfs/
DKconfig22 To compile this as a module, choose M here: the module will be called
29 NCP allows packets to be signed for stronger security. If you want
30 security, say Y. Normal users can leave it off. To be able to use
72 DOS namespace will be converted to lowercase characters.
78 Long filenames (created by Win95) will not be affected.
93 may be useful, if you want to access the server with other operating

123