linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: David Sterba <dsterba@suse.cz>,
	"markus.heininger@online.de" <markus.heininger@online.de>,
	hujianyang <hujianyang@huawei.com>,
	linux-mtd@lists.infradead.org,
	Linux Filesystem Development List <linux-fsdevel@vger.kernel.org>
Subject: Re: UBIFS: Is it possible to get the compressed size of a file?
Date: Tue, 03 Feb 2015 11:07:14 +0200	[thread overview]
Message-ID: <1422954434.8637.372.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <7B8DF06B-EBC8-4C85-AEEA-C2C6A52B8789@dilger.ca>

On Mon, 2015-02-02 at 22:45 -0700, Andreas Dilger wrote:
> I think FIEMAP would be a good userspace API to get this kind of
> low-level allocation information about the compressed size of data.
> For most files it would probably only need a single fiemap_extent
> to return the allocation data.

Thanks Andreas,

indeed FIEMAP sounds like a good answer to the problem.

Artem.


  reply	other threads:[~2015-02-03  9:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <trinity-a1228aa8-8eaa-4950-9c14-5d6b6db5f3d7-1418371801058@3capp-1and1-bs02>
     [not found] ` <54912109.50505@huawei.com>
     [not found]   ` <trinity-03861656-4f4e-47fd-bcc5-aa493202c0bd-1418900934280@3capp-1and1-bs05>
2015-02-02  9:33     ` UBIFS: Is it possible to get the compressed size of a file? Artem Bityutskiy
2015-02-03  5:45       ` Andreas Dilger
2015-02-03  9:07         ` Artem Bityutskiy [this message]
2015-02-28  7:31         ` hujianyang
2015-03-26 14:19           ` 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=1422954434.8637.372.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=adilger@dilger.ca \
    --cc=dsterba@suse.cz \
    --cc=hujianyang@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=markus.heininger@online.de \
    /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).