From: Christoph Hellwig <hch@infradead.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Yu Kuai <yukuai3@huawei.com>,
hch@infradead.org, david@fromorbit.com,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com
Subject: Re: [RFC PATCH V2] iomap: add support to track dirty state of sub pages
Date: Fri, 21 Aug 2020 07:10:19 +0100 [thread overview]
Message-ID: <20200821061019.GD31091@infradead.org> (raw)
In-Reply-To: <20200818165019.GT17456@casper.infradead.org>
On Tue, Aug 18, 2020 at 05:50:19PM +0100, Matthew Wilcox wrote:
> Looks like Christoph changed his mind sometime between that message
> and the first commit: 9dc55f1389f9569acf9659e58dd836a9c70df217
No, as Darrick pointed out it was all about the header dependency.
> My THP patches convert the bit array to be per-block rather than
> per-sector, so this is all going to go away soon ;-)
I've asked a while ago, but let me repeat: Can you split out all the
useful iomap bits that are not directly dependent on the new THP
infrastructure and send them out ASAP? I'd like to pre-load this
work at least a merge window before the actual THP bits.
next prev parent reply other threads:[~2020-08-21 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 13:46 [RFC PATCH V2] iomap: add support to track dirty state of sub pages Yu Kuai
2020-08-18 15:53 ` Matthew Wilcox
2020-08-18 16:12 ` Darrick J. Wong
2020-08-18 16:50 ` Matthew Wilcox
2020-08-18 18:11 ` Darrick J. Wong
2020-08-21 6:10 ` Christoph Hellwig [this message]
2020-08-21 13:05 ` Matthew Wilcox
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=20200821061019.GD31091@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.org \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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.