From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: don't add both copies of DUP to reada extent tree
Date: Sat, 25 Feb 2012 08:33:39 +0000 (UTC) [thread overview]
Message-ID: <pan.2012.02.25.08.33.39@cox.net> (raw)
In-Reply-To: 1330157387-6803-1-git-send-email-sensille@gmx.net
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 both copies reside on the same
> device.
I'm not a coder and thus can't really read the code to know, but wouldn't
the same easier-to-reach logic apply there, only to seeking? One of the
DUPs should be easier to reach (less seeking) than the other.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2012-02-25 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 8:09 [PATCH] btrfs: don't add both copies of DUP to reada extent tree Arne Jansen
2012-02-25 8:33 ` Duncan [this message]
2012-02-25 13:09 ` Arne Jansen
2012-02-25 22:03 ` Duncan
2012-03-15 15:00 ` Andrea Gelmini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2012.02.25.08.33.39@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.