On Thu, Mar 1, 2012 at 4:58 PM, Kevin Wolf wrote:
> Am 01.03.2012 17:22, schrieb Stefan Hajnoczi:
>> On Thu, Mar 01, 2012 at 05:10:57PM +0100, Kevin Wolf wrote:
>>> Am 27.02.2012 14:16, schrieb Stefan Hajnoczi:
The L2 table cache reduces QED metadata reads that would be required
when tra
Am 01.03.2012 17:22, schrieb Stefan Hajnoczi:
> On Thu, Mar 01, 2012 at 05:10:57PM +0100, Kevin Wolf wrote:
>> Am 27.02.2012 14:16, schrieb Stefan Hajnoczi:
>>> The L2 table cache reduces QED metadata reads that would be required
>>> when translating LBAs to offsets into the image file. Since requ
On Thu, Mar 01, 2012 at 05:10:57PM +0100, Kevin Wolf wrote:
> Am 27.02.2012 14:16, schrieb Stefan Hajnoczi:
> > The L2 table cache reduces QED metadata reads that would be required
> > when translating LBAs to offsets into the image file. Since requests
> > execute in parallel it is possible to sh
Am 27.02.2012 14:16, schrieb Stefan Hajnoczi:
> The L2 table cache reduces QED metadata reads that would be required
> when translating LBAs to offsets into the image file. Since requests
> execute in parallel it is possible to share an L2 table between multiple
> requests.
>
> There is a potenti
Tested-by: Benoît Canet
On Mon, Feb 27, 2012 at 2:16 PM, Stefan Hajnoczi <
stefa...@linux.vnet.ibm.com> wrote:
> The L2 table cache reduces QED metadata reads that would be required
> when translating LBAs to offsets into the image file. Since requests
> execute in parallel it is possible to sh
On Mon, Feb 27, 2012 at 1:16 PM, Stefan Hajnoczi
wrote:
> The L2 table cache reduces QED metadata reads that would be required
> when translating LBAs to offsets into the image file. Since requests
> execute in parallel it is possible to share an L2 table between multiple
> requests.
>
> There is