From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>
Cc: kosaki.motohiro@jp.fujitsu.com
Subject: [mmotm][PATCH 0/9] putback_lru_page() rework v5
Date: Tue, 15 Jul 2008 04:06:53 +0900 [thread overview]
Message-ID: <20080715040402.F6EF.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
This patch series is rework of putback_lru_page().
These remove strange unlock_page() from putback_lru_page(),
and improve performance slighly by remove unnecessary lock_page().
Unfortunately current mmotm have tons split-lru related patch
and these depend on each other.
Then, the order of the patches appling is a bit messy.
Please be carefully.
How to apply to this patch series
-----------------------------------------
1. unevictable-lru-infrastructure-putback_lru_page-rework.patch
applies after unevictable-lru-infrastructure-remove-redundant-page-mapping-check.patch
2. unevictable-lru-infrastructure-kill-unnecessary-lock_page.patch
applies after 1.
3. unevictable-lru-infrastructure-revert-migration-change.patch
applies after 2.
4. shm_locked-pages-are-unevictable-revert-shm-change.patch
applies after shm_locked-pages-are-unevictable.patch.
5. replace mlock-mlocked-pages-are-unevictable.patch
to this patch series's one.
6. mlock-mlocked-pages-are-unevictable-resutore-patch-failure-hunk.patch
applies after 5.
7. mlock-mlocked-pages-are-unevictable-putback_lru_page-rework.patch
applies after 6.
8. replace vmstat-unevictable-and-mlocked-pages-vm-events.patch
to this patch series's one.
9. vmstat-unevictable-and-mlocked-pages-vm-events-restore-patch-failure-hunk.patch
applies after 8.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2008-07-14 19:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 19:06 KOSAKI Motohiro [this message]
2008-07-14 19:09 ` [mmotm][PATCH 1/9] putback_lru_page()/unevictable page handling rework KOSAKI Motohiro
2008-07-14 19:10 ` [mmotm][PATCH 2/9] kill unnecessary lock_page() in vmscan.c KOSAKI Motohiro
2008-07-14 19:12 ` [mmotm][PATCH 3/9] revert migration change of unevictable lru infrastructure KOSAKI Motohiro
2008-07-14 19:13 ` [mmotm][PATCH 4/9] revert shm change of shm_locked pages are unevictable patch KOSAKI Motohiro
2008-07-14 19:19 ` [mmotm][PATCH 5/9] mlock-mlocked-pages-are-unevictable.patch KOSAKI Motohiro
2008-07-23 9:07 ` Andrew Morton
2008-07-23 11:55 ` KOSAKI Motohiro
2008-07-24 5:45 ` KOSAKI Motohiro
2008-07-14 19:21 ` [mmotm][PATCH 6/9] restore patch failure hunk of mlock-mlocked-pages-are-unevictable.patch KOSAKI Motohiro
2008-07-14 19:24 ` [mmotm][PATCH 7/9] fix truncate race and sevaral comments KOSAKI Motohiro
2008-07-14 19:26 ` [mmotm][PATCH 8/9] vmstat-unevictable-and-mlocked-pages-vm-events.patch KOSAKI Motohiro
2008-07-14 19:27 ` [mmotm][PATCH 9/9] restore patch failure of vmstat-unevictable-and-mlocked-pages-vm-events.patch KOSAKI Motohiro
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=20080715040402.F6EF.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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