From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: XFS_IOC_FSEMAP requirements
Date: Thu, 22 Dec 2016 00:57:16 -0800 [thread overview]
Message-ID: <20161222085716.GA23054@infradead.org> (raw)
In-Reply-To: <20161221014816.GC5487@birch.djwong.org>
On Tue, Dec 20, 2016 at 05:48:16PM -0800, Darrick J. Wong wrote:
> As for project ideas, I can think of a handful of them -- reworking the
> in-core extent tree not to require large contiguous memory allocations,
> sorting out reflink+dax,
FYI, I have significant work done on both of them. I just need to sort
out the ENOSPC issues (just got another report where we're running into
ENOSPC for inobt updates, so there might be even more dragons there)
and the DAX DIO rework, which is 90% of the work for reflink+DAX.
For the extent tree I played around with a simple rbtree, but I need
to finish abstracting away the access the the extent list - the first
pile of that landed for 4.10, but there is a lot more to be done before
I can easily change the representation. I'm also not sure anymore
that the rbtree is the best choice.
> and stomping out the rest of the buffer head
> usage,
The next for that is the switch bmap and buffered reads for iomap,
I have a version that works for blocksize == page_size, just need
to finish the blocksize < pagesize case. Once get_blocks is gone
we should be able to just kill buffer_heads trivially for the blocksize
== pagesize case, it's just the small block size that will require
a significant effort. My initial plan was to just keep buffer_heads
for those as the first step while not using them for the common
blocksize == pagesize case.
next prev parent reply other threads:[~2016-12-22 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 10:29 XFS_IOC_FSEMAP requirements Carlos Maiolino
2016-12-21 1:48 ` Darrick J. Wong
2016-12-22 8:57 ` Christoph Hellwig [this message]
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=20161222085716.GA23054@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.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).