linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>, viro@zeniv.linux.org.uk
Subject: [PATCH 0/3] fiemap: introduce EXTENT_DATA_COMPRESSED flag
Date: Tue,  3 Sep 2013 14:11:03 +0200	[thread overview]
Message-ID: <cover.1378209377.git.dsterba@suse.cz> (raw)

The original FIEMAP patch did not define this bit, btrfs will make use of
it.  The defined constant maintains the same value as originally proposed.

Currently, the 'filefrag' utility has no way to recognize and denote a
compressed extent. As implemented in btrfs right now, the compression step
splits a big extent into smaller chunks and this is reported as a heavily
fragmented file. Adding the flag to filefrag will at least give some
explanation why, this has been confusing users for some time already.

David Sterba (3):
  fiemap: fix comment at EXTENT_DATA_ENCRYPTED
  fiemap: add EXTENT_DATA_COMPRESSED flag
  btrfs: set FIEMAP_EXTENT_DATA_COMPRESSED for compressed extents

 fs/btrfs/extent_io.c        |    4 +++-
 include/uapi/linux/fiemap.h |    4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

-- 
1.7.9


             reply	other threads:[~2013-09-03 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 12:11 David Sterba [this message]
2013-09-03 12:11 ` [PATCH 1/3] fiemap: fix comment at EXTENT_DATA_ENCRYPTED David Sterba
2013-09-03 12:11 ` [PATCH 2/3] fiemap: add EXTENT_DATA_COMPRESSED flag David Sterba
2013-09-06  5:28   ` Andreas Dilger
2013-09-09 22:06     ` David Sterba
2013-09-03 12:11 ` [PATCH 3/3] btrfs: set FIEMAP_EXTENT_DATA_COMPRESSED for compressed extents 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=cover.1378209377.git.dsterba@suse.cz \
    --to=dsterba@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).