From: Josef Bacik <josef@redhat.com>
To: Andrew Mahone <andrew.mahone@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: PATCH: btrfs defrag ioctl, override extent count and size checks compression enabled.
Date: Fri, 15 Jun 2012 11:57:28 -0400 [thread overview]
Message-ID: <20120615155728.GB1556@localhost.localdomain> (raw)
In-Reply-To: <CAOUOUDzAEe8mZwrtqaFyQ1B9B8AFOhxyv5X70uQCPbVzYk8v+g@mail.gmail.com>
On Tue, Jun 05, 2012 at 12:21:40PM -0400, Andrew Mahone wrote:
> I noticed a few days ago that btrfs fi defrag -cXXX can not be used to
> compress files unless they are fragmented. The attached patch passes
> the compression flag to should_defrag_range, where it disables the
> adjacent-extent and extent size checks if set. The inline/sparse
> extent check is not modified - I assumed it would not be useful to
> compress inline extents.
>
Need a Signed-off-by: line and please inline your patches, don't attach them.
Once you resubmit I'll include in btrfs-next. Thanks,
Josef
prev parent reply other threads:[~2012-06-15 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 16:21 PATCH: btrfs defrag ioctl, override extent count and size checks compression enabled Andrew Mahone
2012-06-15 15:57 ` Josef Bacik [this message]
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=20120615155728.GB1556@localhost.localdomain \
--to=josef@redhat.com \
--cc=andrew.mahone@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).