Home
last modified time | relevance | path

Searched refs:fsblock (Results 1 – 3 of 3) sorted by relevance

/linux/fs/omfs/
H A Ddir.c317 u64 fsblock) in omfs_is_bad() argument
321 is_bad = ((ino != fsblock) || (ino < sbi->s_root_ino) || in omfs_is_bad()
331 u64 fsblock, int hindex) in omfs_fill_chain() argument
334 while (fsblock != ~0) { in omfs_fill_chain()
335 struct buffer_head *bh = omfs_bread(dir->i_sb, fsblock); in omfs_fill_chain()
344 if (omfs_is_bad(OMFS_SB(dir->i_sb), &oi->i_head, fsblock)) { in omfs_fill_chain()
349 self = fsblock; in omfs_fill_chain()
350 fsblock = be64_to_cpu(oi->i_sibling); in omfs_fill_chain()
438 __u64 fsblock = be64_to_cpu(*p++); in omfs_readdir() local
439 if (!omfs_fill_chain(dir, ctx, fsblock, hindex)) in omfs_readdir()
H A Domfs.h52 u64 fsblock);
/linux/Documentation/filesystems/iomap/
H A Doperations.rst162 If the fsblock size matches the size of a pagecache folio, it is assumed
168 If the fsblock size is less than the size of a pagecache folio, iomap
169 tracks the per-fsblock uptodate and dirty state itself.
174 iomap internally tracks two state bits per fsblock:
184 The folio itself will be marked dirty when any fsblock within the
190 because there is only one per folio, and the per-fsblock overhead is two
275 the fsblock size.
296 pagecache from EOF to the end of the fsblock during a file truncation
741 Regions of the pagecache with no folio mapped, or a !uptodate fsblock