Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Yu Kuai <yukuai3@huawei.com>
Cc: hch@infradead.org, darrick.wong@oracle.com, 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 V4] iomap: add support to track dirty state of sub pages
Date: Fri, 21 Aug 2020 13:44:24 +0100 [thread overview]
Message-ID: <20200821124424.GQ17456@casper.infradead.org> (raw)
In-Reply-To: <20200821123306.1658495-1-yukuai3@huawei.com>
On Fri, Aug 21, 2020 at 08:33:06PM +0800, Yu Kuai wrote:
> changes from v3:
> - add IOMAP_STATE_ARRAY_SIZE
> - replace set_bit / clear_bit with bitmap_set / bitmap_clear
> - move iomap_set_page_dirty() out of 'iop->state_lock'
> - merge iomap_set/clear_range_dirty() and iomap_iop_clear/clear_range_dirty()
I'm still working on the iomap parts of the THP series (fixing up
invalidatepage right now), but here are some of the relevant bits (patch
series to follow)
next prev parent reply other threads:[~2020-08-21 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 12:33 Yu Kuai
2020-08-21 12:44 ` Matthew Wilcox [this message]
2020-08-21 12:46 ` [PATCH 1/3] iomap: Use kzalloc to allocate iomap_page Matthew Wilcox (Oracle)
2020-08-21 12:46 ` [PATCH 2/3] iomap: Use bitmap ops to set uptodate bits Matthew Wilcox (Oracle)
2020-08-22 5:59 ` Christoph Hellwig
2020-08-21 12:46 ` [PATCH 3/3] iomap: Support arbitrarily many blocks per page Matthew Wilcox (Oracle)
2020-08-21 12:48 ` Matthew Wilcox
2020-08-22 6:01 ` Christoph Hellwig
2020-08-22 5:57 ` [PATCH 1/3] iomap: Use kzalloc to allocate iomap_page Christoph Hellwig
2020-09-11 8:27 ` [RFC PATCH V4] iomap: add support to track dirty state of sub pages yukuai (C)
2020-09-11 8:35 ` yukuai (C)
2020-09-11 12:05 ` Matthew Wilcox
2020-09-25 2:30 ` yukuai (C)
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=20200821124424.GQ17456@casper.infradead.org \
--to=willy@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
--subject='Re: [RFC PATCH V4] iomap: add support to track dirty state of sub pages' \
/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
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).