QCOW uses two tables level1 (L1) table and level2
(L2) table. The L1 table points to offset of L2
table. When a QCOW image is probed, the L1 table is
cached in the memory to avoid reading it from disk
on every reference. This caching imporves the
performance. The similar performance improvment can
On Wed, May 18, 2011 at 1:17 PM, Prasad Joshi prasadjoshi...@gmail.com wrote:
QCOW uses two tables level1 (L1) table and level2
(L2) table. The L1 table points to offset of L2
table. When a QCOW image is probed, the L1 table is
cached in the memory to avoid reading it from disk
on every
On Wed, May 18, 2011 at 11:27 AM, Pekka Enberg penb...@kernel.org wrote:
On Wed, May 18, 2011 at 1:17 PM, Prasad Joshi prasadjoshi...@gmail.com
wrote:
QCOW uses two tables level1 (L1) table and level2
(L2) table. The L1 table points to offset of L2
table. When a QCOW image is probed, the L1
* Pekka Enberg penb...@kernel.org wrote:
On Wed, May 18, 2011 at 1:17 PM, Prasad Joshi prasadjoshi...@gmail.com
wrote:
QCOW uses two tables level1 (L1) table and level2
(L2) table. The L1 table points to offset of L2
table. When a QCOW image is probed, the L1 table is
cached in the
On Wed, May 18, 2011 at 1:41 PM, Prasad Joshi prasadjoshi...@gmail.com wrote:
On Wed, May 18, 2011 at 11:27 AM, Pekka Enberg penb...@kernel.org wrote:
On Wed, May 18, 2011 at 1:17 PM, Prasad Joshi prasadjoshi...@gmail.com
wrote:
QCOW uses two tables level1 (L1) table and level2
(L2) table.
On Wed, 2011-05-18 at 11:17 +0100, Prasad Joshi wrote:
QCOW uses two tables level1 (L1) table and level2
(L2) table. The L1 table points to offset of L2
table. When a QCOW image is probed, the L1 table is
cached in the memory to avoid reading it from disk
on every reference. This caching
