Lines Matching full:l2

2  * QEMU Enhanced Disk Format L2 Cache
15  * L2 table cache usage is as follows:
17  * An open image has one L2 table cache that is used to avoid accessing the
18  * image file for recently referenced L2 tables.
22  * the L1 and L2 tables which store cluster offsets.  It is here where the L2
23  * table cache serves up recently referenced L2 tables.
25  * If there is a cache miss, that L2 table is read from the image file and
26  * committed to the cache.  Subsequent accesses to that L2 table will be served
29  * L2 tables are also committed to the cache when new L2 tables are allocated
30  * in the image file.  Since the L2 table cache is write-through, the new L2
34  * Multiple I/O requests may be using an L2 table cache entry at any given
40  * An in-flight I/O request will hold a reference to a L2 table cache entry for
41  * the period during which it needs to access the L2 table.  This includes
42  * cluster offset lookup, L2 table allocation, and L2 table update when a new
45  * An interesting case occurs when two requests need to access an L2 table that
48  * start reading the L2 table from the image file.  The first to finish will
49  * commit its L2 table into the cache.  When the second tries to commit its
58 /* Each L2 holds 2GB so this let's us fully cache a 100GB disk */
62  * Initialize the L2 cache
71  * Free the L2 cache
123  * Find an entry in the L2 cache.  This may return NULL and it's up to the
146  * Commit an L2 cache entry into the cache.  This is meant to be used as part of
148  * is not actually in the L2 cache and then once the entry was valid and