From: Gao Xiang <gaoxiang25@huawei.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
Chao Yu <yuchao0@huawei.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
<linux-xfs@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<chao@kernel.org>
Subject: Re: [RFC PATCH] iomap: generalize IOMAP_INLINE to cover tail-packing case
Date: Thu, 18 Jul 2019 21:27:41 +0800 [thread overview]
Message-ID: <cb859e68-1f7f-48a6-593b-4047963086ba@huawei.com> (raw)
In-Reply-To: <20190718123155.GA21252@infradead.org>
On 2019/7/18 20:31, Christoph Hellwig wrote:
> That being said until the tail packing fs (erofs?) actually uses
> buffer_heads we should not need this hunk, and I don't think erofs
> should have any reason to use buffer_heads.
Yes, erofs will not use buffer_head to support sub-page blocksize
in the long term. too heavy and no need...
Thanks,
Gao Xiang
WARNING: multiple messages have this Message-ID (diff)
From: Gao Xiang <gaoxiang25@huawei.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
Chao Yu <yuchao0@huawei.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
chao@kernel.org
Subject: Re: [RFC PATCH] iomap: generalize IOMAP_INLINE to cover tail-packing case
Date: Thu, 18 Jul 2019 21:27:41 +0800 [thread overview]
Message-ID: <cb859e68-1f7f-48a6-593b-4047963086ba@huawei.com> (raw)
In-Reply-To: <20190718123155.GA21252@infradead.org>
On 2019/7/18 20:31, Christoph Hellwig wrote:
> That being said until the tail packing fs (erofs?) actually uses
> buffer_heads we should not need this hunk, and I don't think erofs
> should have any reason to use buffer_heads.
Yes, erofs will not use buffer_head to support sub-page blocksize
in the long term. too heavy and no need...
Thanks,
Gao Xiang
next prev parent reply other threads:[~2019-07-18 13:27 UTC|newest]
Thread overview: 26+ 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-03 7:55 ` Chao Yu
2019-07-08 2:12 ` 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 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 9:31 ` Chao Yu
2019-07-12 11:54 ` Andreas Gruenbacher
2019-07-15 9:26 ` Chao Yu
2019-07-15 9:26 ` Chao Yu
2019-07-17 2:58 ` Chao Yu
2019-07-17 2:58 ` Chao Yu
2019-07-18 12:33 ` Christoph Hellwig
2019-07-18 12:31 ` Christoph Hellwig
2019-07-18 13:27 ` Gao Xiang [this message]
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=cb859e68-1f7f-48a6-593b-4047963086ba@huawei.com \
--to=gaoxiang25@huawei.com \
--cc=agruenba@redhat.com \
--cc=chao@kernel.org \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.