From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: Chao Yu <yuchao0@huawei.com>,
Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Gao Xiang <gaoxiang25@huawei.com>,
chao@kernel.org
Subject: Re: [RFC PATCH] iomap: generalize IOMAP_INLINE to cover tail-packing case
Date: Thu, 18 Jul 2019 05:33:09 -0700 [thread overview]
Message-ID: <20190718123309.GB21252@infradead.org> (raw)
In-Reply-To: <CAHc6FU5tBXeJ6xzZzfCQeaQFy-NZ5ryZ+QMGLu7yxcGXwYisNw@mail.gmail.com>
On Fri, Jul 12, 2019 at 01:54:07PM +0200, Andreas Gruenbacher wrote:
> Yes, probably by returning i_blocksize(inode) after
> iomap_read_inline_data, but that alone isn't enough to make the patch
> work completely. This really needs a review from Christoph and careful
> testing of all the code paths.
Well, lets start with the testing. Can we get a coherent series that
includes the erofs bits?
next prev parent reply other threads:[~2019-07-18 12:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 7:55 [RFC PATCH] iomap: generalize IOMAP_INLINE to cover tail-packing case Chao Yu
2019-07-08 2:12 ` Chao Yu
2019-07-08 16:03 ` Christoph Hellwig
2019-07-09 13:52 ` Chao Yu
2019-07-09 23:32 ` Andreas Grünbacher
2019-07-10 10:30 ` Chao Yu
2019-07-10 21:50 ` Andreas Grünbacher
2019-07-10 23:42 ` Gao Xiang
2019-07-11 13:06 ` Matthew Wilcox
2019-07-11 13:54 ` Gao Xiang
2019-07-11 14:15 ` Chao Yu
2019-07-11 12:28 ` Andreas Gruenbacher
2019-07-12 9:31 ` Chao Yu
2019-07-12 11:54 ` Andreas Gruenbacher
2019-07-15 9:26 ` Chao Yu
2019-07-17 2:58 ` Chao Yu
2019-07-18 12:33 ` Christoph Hellwig [this message]
2019-07-18 12:31 ` Christoph Hellwig
2019-07-18 13:27 ` Gao Xiang
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=20190718123309.GB21252@infradead.org \
--to=hch@infradead.org \
--cc=agruenba@redhat.com \
--cc=chao@kernel.org \
--cc=darrick.wong@oracle.com \
--cc=gaoxiang25@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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).