From: Matthew Wilcox <willy@infradead.org>
To: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: [PATCH v2 0/5] Make PageWriteback use the PageLocked optimisation
Date: Thu, 16 Apr 2020 08:46:01 -0700 [thread overview]
Message-ID: <20200416154606.306-1-willy@infradead.org> (raw)
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
PageWaiters is used by PageWriteback and PageLocked (and no other page
flags), so it makes sense to use the same codepaths that have already been
optimised for PageLocked, even if there's probably no real performance
benefit to be had.
v2: Rebased to 5.7-rc1
- Split up patches better
- Moved the BUG() from end_page_writeback() to __clear_page_writeback()
as requested by Jan Kara.
- Converted the BUG() to WARN_ON()
- Removed TestClearPageWriteback
Matthew Wilcox (Oracle) (5):
mm: Remove definition of clear_bit_unlock_is_negative_byte
mm: Move PG_writeback into the bottom byte
mm: Convert writeback BUG to WARN_ON
mm: Use clear_bit_unlock_is_negative_byte for PageWriteback
mm: Remove TestClearPageWriteback
include/linux/page-flags.h | 8 ++++----
mm/filemap.c | 41 +++++--------------------------------
mm/page-writeback.c | 42 +++++++++++++++++++++++---------------
3 files changed, 34 insertions(+), 57 deletions(-)
--
2.25.1
next reply other threads:[~2020-04-16 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 15:46 Matthew Wilcox [this message]
2020-04-16 15:46 ` [PATCH v2 1/5] mm: Remove definition of clear_bit_unlock_is_negative_byte Matthew Wilcox
2020-04-16 17:02 ` Will Deacon
2020-04-16 17:13 ` Matthew Wilcox
2020-04-16 15:46 ` [PATCH v2 2/5] mm: Move PG_writeback into the bottom byte Matthew Wilcox
2020-04-16 15:46 ` [PATCH v2 3/5] mm: Convert writeback BUG to WARN_ON Matthew Wilcox
2020-04-16 15:46 ` [PATCH v2 4/5] mm: Use clear_bit_unlock_is_negative_byte for PageWriteback Matthew Wilcox
2020-04-16 15:46 ` [PATCH v2 5/5] mm: Remove TestClearPageWriteback 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=20200416154606.306-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.