Lines Matching refs:node

93 - Use a term, “node”, that represents inodes as well as various pointer blocks
94 - Introduce Node Address Table (NAT) containing the locations of all the “node”
366 			 pending node write	drop		keep		N/A
558    It is composed of a block address table for all the node blocks stored in
563    data and node blocks stored in Main area.
604 The key data structure to manage the data locations is a "node". Similar to
605 traditional file structures, F2FS has three types of node: inode, direct node,
606 indirect node. F2FS assigns 4KB to an inode block which contains 923 data block
607 indices, two direct node pointers, two indirect node pointers, and one double
608 indirect node pointer as described below. One direct node block contains 1018
609 data blocks, and one indirect node block contains also 1018 node blocks. Thus,
616      |- direct node (2)
618      |- indirect node (2)
619      |            `- direct node (1018)
621      `- double indirect node (1)
622                          `- indirect node (1018)
623 			              `- direct node (1018)
626 Note that all the node blocks are mapped by NAT which means the location of
627 each node is translated by the NAT table. In the consideration of the wandering
628 tree problem, F2FS is able to cut off the propagation of node updates caused by
733 At runtime, F2FS manages six active logs inside "Main" area: Hot/Warm/Cold node
736 - Hot node	contains direct node blocks of directories.
737 - Warm node	contains direct node blocks except hot node blocks.
738 - Cold node	contains indirect node blocks
955 the usual f2fs node structures. This mapped area is pinned and primarily intended