Lines Matching full:table

15  * L2 table cache usage is as follows:
17  * An open image has one L2 table cache that is used to avoid accessing the
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
27  * from the cache until the table is evicted from the cache.
30  * in the image file.  Since the L2 table cache is write-through, the new L2
31  * table is first written out to the image file and then committed to the
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
46  * is not in the cache.  Since the operation to read the table from the image
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
50  * table will be deleted in favor of the existing cache entry.
78         qemu_vfree(entry->table);  in qed_free_l2_cache()
87  * The caller must allocate the actual table field for this entry and it must
117         qemu_vfree(entry->table);  in qed_unref_l2_cache_entry()