Re: [PATCH] btrfs: don't add both copies of DUP to reada extent tree

2012-03-15 Thread Andrea Gelmini
On Sat, Feb 25, 2012 at 09:09:47AM +0100, Arne Jansen wrote: > Normally when there are 2 copies of a block, we add both to the > reada extent tree and prefetch only the one that is easier to reach. > This way we can better utilize multiple devices. > In case of DUP this makes no sense as both copie

Re: [PATCH] btrfs: don't add both copies of DUP to reada extent tree

2012-02-25 Thread Duncan
Arne Jansen posted on Sat, 25 Feb 2012 14:09:50 +0100 as excerpted: > On 02/25/12 09:33, Duncan wrote: >> Arne Jansen posted on Sat, 25 Feb 2012 09:09:47 +0100 as excerpted: >> >>> Normally when there are 2 copies of a block, we add both to the reada >>> extent tree and prefetch only the one that

Re: [PATCH] btrfs: don't add both copies of DUP to reada extent tree

2012-02-25 Thread Arne Jansen
On 02/25/12 09:33, Duncan wrote: Arne Jansen posted on Sat, 25 Feb 2012 09:09:47 +0100 as excerpted: Normally when there are 2 copies of a block, we add both to the reada extent tree and prefetch only the one that is easier to reach. This way we can better utilize multiple devices. In case of D

Re: [PATCH] btrfs: don't add both copies of DUP to reada extent tree

2012-02-25 Thread Duncan
Arne Jansen posted on Sat, 25 Feb 2012 09:09:47 +0100 as excerpted: > Normally when there are 2 copies of a block, we add both to the reada > extent tree and prefetch only the one that is easier to reach. > This way we can better utilize multiple devices. > In case of DUP this makes no sense as bo

[PATCH] btrfs: don't add both copies of DUP to reada extent tree

2012-02-25 Thread Arne Jansen
Normally when there are 2 copies of a block, we add both to the reada extent tree and prefetch only the one that is easier to reach. This way we can better utilize multiple devices. In case of DUP this makes no sense as both copies reside on the same device. Signed-off-by: Arne Jansen --- fs/btr