linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: XFS_IOC_FSEMAP requirements
Date: Tue, 20 Dec 2016 11:29:35 +0100	[thread overview]
Message-ID: <20161220102935.ppt7ixjoh53uhu2e@eorzea.usersys.redhat.com> (raw)

Hi folks,

I've been working on the implementation of FSEMAP ioctl as we've been discussed
previously, and, the first discussion about this, was about using the same
fiemap structures to retrieve free extents from the btrees.

By our last chat about it (it's been a while, I know, I got busy with more
important stuff :), Dave suggested another uses for FSEMAP that were not in my
mind, so, I think it deserves its own implementation, independent of fiemap from
where the same idea came from.

So, I'd like to know, what else might FSEMAP be used for, beyond iterating free
space extents, so I can think of a new struct to be exchanged between user<->
kernel. FSEMAP is supposed to complement GETFSMAPX, discussed in LSF this year,
but I don't know if is there any plan to keep with GETFSMAPX or not, or even if
FSEMAP is still a valuable idea :)

Any comments, suggestions about to what direction should FSEMAP go?

Cheers
-- 
Carlos

             reply	other threads:[~2016-12-20 10:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 10:29 Carlos Maiolino [this message]
2016-12-21  1:48 ` XFS_IOC_FSEMAP requirements Darrick J. Wong
2016-12-22  8:57   ` Christoph Hellwig
2016-12-22 20:07     ` Dave Chinner
2016-12-22 20:24       ` Christoph Hellwig
2016-12-22  9:28   ` Carlos Maiolino

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=20161220102935.ppt7ixjoh53uhu2e@eorzea.usersys.redhat.com \
    --to=cmaiolino@redhat.com \
    --cc=linux-xfs@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).