diff options
author | Fengguang Wu <wfg@mail.ustc.edu.cn> | 2007-07-19 04:48:07 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-07-19 13:04:44 -0400 |
commit | fe3cba17c49471e99d3421e675fc8b3deaaf0b70 (patch) | |
tree | df696c4584c6db2e439f068d2474fcb946ca587d /mm/page_alloc.c | |
parent | d8983910a4045fa21022cfccf76ed13eb40fd7f5 (diff) |
mm: share PG_readahead and PG_reclaim
Share the same page flag bit for PG_readahead and PG_reclaim.
One is used only on file reads, another is only for emergency writes. One
is used mostly for fresh/young pages, another is for old pages.
Combinations of possible interactions are:
a) clear PG_reclaim => implicit clear of PG_readahead
it will delay an asynchronous readahead into a synchronous one
it actually does _good_ for readahead:
the pages will be reclaimed soon, it's readahead thrashing!
in this case, synchronous readahead makes more sense.
b) clear PG_readahead => implicit clear of PG_reclaim
one(and only one) page will not be reclaimed in time
it can be avoided by checking PageWriteback(page) in readahead first
c) set PG_reclaim => implicit set of PG_readahead
will confuse readahead and make it restart the size rampup process
it's a trivial problem, and can mostly be avoided by checking
PageWriteback(page) first in readahead
d) set PG_readahead => implicit set of PG_reclaim
PG_readahead will never be set on already cached pages.
PG_reclaim will always be cleared on dirtying a page.
so not a problem.
In summary,
a) we get better behavior
b,d) possible interactions can be avoided
c) racy condition exists that might affect readahead, but the chance
is _really_ low, and the hurt on readahead is trivial.
Compound pages also use PG_reclaim, but for now they do not interact with
reclaim/readahead code.
Signed-off-by: Fengguang Wu <wfg@mail.ustc.edu.cn>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/page_alloc.c')
-rw-r--r-- | mm/page_alloc.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 2165be9462c0..43cb3b3e1679 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c | |||
@@ -453,12 +453,6 @@ static inline int free_pages_check(struct page *page) | |||
453 | 1 << PG_reserved | | 453 | 1 << PG_reserved | |
454 | 1 << PG_buddy )))) | 454 | 1 << PG_buddy )))) |
455 | bad_page(page); | 455 | bad_page(page); |
456 | /* | ||
457 | * PageReclaim == PageTail. It is only an error | ||
458 | * for PageReclaim to be set if PageCompound is clear. | ||
459 | */ | ||
460 | if (unlikely(!PageCompound(page) && PageReclaim(page))) | ||
461 | bad_page(page); | ||
462 | if (PageDirty(page)) | 456 | if (PageDirty(page)) |
463 | __ClearPageDirty(page); | 457 | __ClearPageDirty(page); |
464 | /* | 458 | /* |
@@ -602,7 +596,6 @@ static int prep_new_page(struct page *page, int order, gfp_t gfp_flags) | |||
602 | 1 << PG_locked | | 596 | 1 << PG_locked | |
603 | 1 << PG_active | | 597 | 1 << PG_active | |
604 | 1 << PG_dirty | | 598 | 1 << PG_dirty | |
605 | 1 << PG_reclaim | | ||
606 | 1 << PG_slab | | 599 | 1 << PG_slab | |
607 | 1 << PG_swapcache | | 600 | 1 << PG_swapcache | |
608 | 1 << PG_writeback | | 601 | 1 << PG_writeback | |