From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: andrea@betterlinux.com
Cc: akpm@linux-foundation.org, minchan.kim@gmail.com,
riel@redhat.com, peterz@infradead.org, hannes@cmpxchg.org,
kamezawa.hiroyu@jp.fujitsu.com, aarcange@redhat.com,
hughd@google.com, jamesjer@betterlinux.com, marcus@bluehost.com,
matt@bluehost.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] fadvise: move active pages to inactive list with POSIX_FADV_DONTNEED
Date: Thu, 23 Jun 2011 12:15:26 +0900 [thread overview]
Message-ID: <4E02AFCE.6000604@jp.fujitsu.com> (raw)
In-Reply-To: <1308779480-4950-1-git-send-email-andrea@betterlinux.com>
(2011/06/23 6:51), Andrea Righi wrote:
> There were some reported problems in the past about trashing page cache
> when a backup software (i.e., rsync) touches a huge amount of pages (see
> for example [1]).
>
> This problem has been almost fixed by the Minchan Kim's patch [2] and a
> proper use of fadvise() in the backup software. For example this patch
> set [3] has been proposed for inclusion in rsync.
>
> However, there can be still other similar trashing problems: when the
> backup software reads all the source files, some of them may be part of
> the actual working set of the system. When a
> posix_fadvise(POSIX_FADV_DONTNEED) is performed _all_ pages are evicted
> from pagecache, both the working set and the use-once pages touched only
> by the backup software.
>
> With the following solution when posix_fadvise(POSIX_FADV_DONTNEED) is
> called for an active page instead of removing it from the page cache it
> is added to the tail of the inactive list. Otherwise, if it's already in
> the inactive list the page is removed from the page cache.
>
> In this way if the backup was the only user of a page, that page will
> be immediately removed from the page cache by calling
> posix_fadvise(POSIX_FADV_DONTNEED). If the page was also touched by
> other processes it'll be moved to the inactive list, having another
> chance of being re-added to the working set, or simply reclaimed when
> memory is needed.
>
> Testcase:
>
> - create a 1GB file called "zero"
> - run md5sum zero to read all the pages in page cache (this is to
> simulate the user activity on this file)
> - run "rsync zero zero_copy" (rsync is patched with [3])
> - re-run md5sum zero (user activity on the working set) and measure
> the time to complete this command
>
> The test has been performed using 3.0.0-rc4 vanilla and with this patch
> applied (3.0.0-rc4-fadvise).
>
> Results:
> avg elapsed time block:block_bio_queue
> 3.0.0-rc4 4.127s 8,214
> 3.0.0-rc4-fadvise 2.146s 0
>
> In the first case the file is evicted from page cache completely and we
> must re-read it from the disk. In the second case the file is still in
> page cache (in the inactive list) and we don't need any other additional
> I/O operation.
>
> [1] http://marc.info/?l=rsync&m=128885034930933&w=2
> [2] https://lkml.org/lkml/2011/2/20/57
> [3] http://lists.samba.org/archive/rsync/2010-November/025827.html
>
> Signed-off-by: Andrea Righi <andrea@betterlinux.com>
> ---
> mm/swap.c | 9 +++++----
> mm/truncate.c | 5 ++++-
> 2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/mm/swap.c b/mm/swap.c
> index 3a442f1..fc8bb76 100644
> --- a/mm/swap.c
> +++ b/mm/swap.c
> @@ -411,10 +411,11 @@ void add_page_to_unevictable_list(struct page *page)
> *
> * 1. active, mapped page -> none
> * 2. active, dirty/writeback page -> inactive, head, PG_reclaim
> - * 3. inactive, mapped page -> none
> - * 4. inactive, dirty/writeback page -> inactive, head, PG_reclaim
> - * 5. inactive, clean -> inactive, tail
> - * 6. Others -> none
> + * 3. active, clean -> inactive, tail
> + * 4. inactive, mapped page -> none
> + * 5. inactive, dirty/writeback page -> inactive, head, PG_reclaim
> + * 6. inactive, clean -> inactive, tail
> + * 7. Others -> none
> *
> * In 4, why it moves inactive's head, the VM expects the page would
> * be write it out by flusher threads as this is much more effective
> diff --git a/mm/truncate.c b/mm/truncate.c
> index 3a29a61..043aabd 100644
> --- a/mm/truncate.c
> +++ b/mm/truncate.c
> @@ -357,7 +357,10 @@ unsigned long invalidate_mapping_pages(struct address_space *mapping,
> if (lock_failed)
> continue;
>
> - ret = invalidate_inode_page(page);
> + if (PageActive(page))
> + ret = 0;
> + else
> + ret = invalidate_inode_page(page);
So, after this patch, following comment is a bit outdated. we deactivate
the page even if it's not invalidated.
/*
* Invalidation is a hint that the page is no longer
* of interest and try to speed up its reclaim.
*/
Can you please fix the comment too? Other than that,
Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-23 3:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 21:51 [PATCH RFC] fadvise: move active pages to inactive list with POSIX_FADV_DONTNEED Andrea Righi
2011-06-22 23:04 ` Rik van Riel
2011-06-23 3:15 ` KOSAKI Motohiro [this message]
2011-06-23 6:18 ` Andrea Righi
2011-06-23 11:14 ` Pádraig Brady
2011-06-23 13:57 ` Andrea Righi
2011-06-23 14:14 ` Pádraig Brady
2011-06-23 15:32 ` Andrea Righi
2011-06-27 5:38 ` KOSAKI Motohiro
2011-06-27 9:17 ` Pádraig Brady
2011-06-27 9:44 ` 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=4E02AFCE.6000604@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andrea@betterlinux.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jamesjer@betterlinux.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcus@bluehost.com \
--cc=matt@bluehost.com \
--cc=minchan.kim@gmail.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).