From: Mitch Harder <mitch.harder@sabayonlinux.org>
To: dave@jikos.cz, Mitch Harder <mitch.harder@sabayonlinux.org>,
linux-btrfs@vger.kernel.org, zab@redhat.com
Subject: Re: [RFC] Btrfs: Allow the compressed extent size limit to be modified v2
Date: Thu, 7 Feb 2013 23:17:46 -0600 [thread overview]
Message-ID: <CAKcLGm_z+bMYtBZYvQYRXrPVHxEfrnfaVNPo8=qeKb3JSUOgiw@mail.gmail.com> (raw)
In-Reply-To: <20130208002854.GA1575@twin.jikos.cz>
On Thu, Feb 7, 2013 at 6:28 PM, David Sterba <dave@jikos.cz> wrote:
> On Thu, Feb 07, 2013 at 03:38:34PM -0600, Mitch Harder wrote:
>> --- a/fs/btrfs/relocation.c
>> +++ b/fs/btrfs/relocation.c
>> @@ -144,7 +144,7 @@ struct tree_block {
>> unsigned int key_ready:1;
>> };
>>
>> -#define MAX_EXTENTS 128
>> +#define MAX_EXTENTS 512
>
> Is this really related to compression? IIRC I've seen it only in context
> of batch work in reloc, but not anywhere near compression. (I may be
> wrong of course, just checking).
>
When you defragment compressed extents, it will run through relocation.
If autodefrag is enabled, I found most everything I touched was
running through relocation.
It has been a while since I looked at the issue, but I think balancing
your data will also run through relocation.
next prev parent reply other threads:[~2013-02-08 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 21:38 [RFC] Btrfs: Allow the compressed extent size limit to be modified v2 Mitch Harder
2013-02-07 22:18 ` Zach Brown
2013-02-08 0:28 ` David Sterba
2013-02-08 5:17 ` Mitch Harder [this message]
2013-02-08 14:53 ` David Sterba
2013-02-08 15:13 ` Mitch Harder
2013-02-20 12:59 ` David Sterba
2013-02-20 14:20 ` Liu Bo
2013-02-26 18:12 ` David Sterba
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='CAKcLGm_z+bMYtBZYvQYRXrPVHxEfrnfaVNPo8=qeKb3JSUOgiw@mail.gmail.com' \
--to=mitch.harder@sabayonlinux.org \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=zab@redhat.com \
/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.