From: Rik van Riel <riel@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mel@csn.ul.ie
Subject: Re: [PATCH] vmscan: improve reclaim throuput to bail out patch
Date: Wed, 03 Dec 2008 08:46:23 -0500 [thread overview]
Message-ID: <49368DAF.9060206@redhat.com> (raw)
In-Reply-To: <20081203140419.1D44.KOSAKI.MOTOHIRO@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> Hi
>
> I evaluate rvr bailout and skip-freeing patch in this week conteniously.
> I'd like to dump first output here.
>
>
>
> Rik, could you please review following?
> ==
> vmscan bail out patch move nr_reclaimed variable to struct scan_control.
> Unfortunately, indirect access can easily happen cache miss.
> More unfortunately, Some architecture (e.g. ia64) don't access global
> variable so fast.
That is amazing. Especially considering that the scan_control
is a local variable on the stack.
> if heavy memory pressure happend, that's ok.
> cache miss already plenty. it is not observable.
>
> but, if memory pressure is lite, performance degression is obserbable.
> about 4-5% degression.
>
> Then, this patch introduce temporal local variable.
> OK. the degression is disappeared.
I can't argue with the numbers, though :)
Maybe all the scanning we do ends up evicting the cache lines
with the scan_control struct in it from the fast part of the
CPU cache?
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Acked-by: Rik van Riel <riel@redhat.com>
--
All rights reversed.
WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mel@csn.ul.ie
Subject: Re: [PATCH] vmscan: improve reclaim throuput to bail out patch
Date: Wed, 03 Dec 2008 08:46:23 -0500 [thread overview]
Message-ID: <49368DAF.9060206@redhat.com> (raw)
In-Reply-To: <20081203140419.1D44.KOSAKI.MOTOHIRO@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> Hi
>
> I evaluate rvr bailout and skip-freeing patch in this week conteniously.
> I'd like to dump first output here.
>
>
>
> Rik, could you please review following?
> ==
> vmscan bail out patch move nr_reclaimed variable to struct scan_control.
> Unfortunately, indirect access can easily happen cache miss.
> More unfortunately, Some architecture (e.g. ia64) don't access global
> variable so fast.
That is amazing. Especially considering that the scan_control
is a local variable on the stack.
> if heavy memory pressure happend, that's ok.
> cache miss already plenty. it is not observable.
>
> but, if memory pressure is lite, performance degression is obserbable.
> about 4-5% degression.
>
> Then, this patch introduce temporal local variable.
> OK. the degression is disappeared.
I can't argue with the numbers, though :)
Maybe all the scanning we do ends up evicting the cache lines
with the scan_control struct in it from the fast part of the
CPU cache?
> Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Acked-by: Rik van Riel <riel@redhat.com>
--
All rights reversed.
--
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 prev parent reply other threads:[~2008-12-03 13:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 19:50 [PATCH] vmscan: bail out of page reclaim after swap_cluster_max pages Rik van Riel
2008-11-24 19:50 ` Rik van Riel
2008-11-24 20:53 ` Andrew Morton
2008-11-24 20:53 ` Andrew Morton
2008-11-25 11:35 ` KOSAKI Motohiro
2008-11-25 11:35 ` KOSAKI Motohiro
2008-11-25 13:32 ` Rik van Riel
2008-11-25 13:32 ` Rik van Riel
2008-11-25 14:30 ` KOSAKI Motohiro
2008-11-25 14:30 ` KOSAKI Motohiro
2008-11-28 7:02 ` KOSAKI Motohiro
2008-11-28 7:02 ` KOSAKI Motohiro
2008-11-28 11:03 ` Rik van Riel
2008-11-28 11:03 ` Rik van Riel
2008-11-29 10:53 ` KOSAKI Motohiro
2008-11-29 10:53 ` KOSAKI Motohiro
2008-11-29 16:24 ` Rik van Riel
2008-11-29 16:24 ` Rik van Riel
2008-11-30 6:30 ` KOSAKI Motohiro
2008-11-30 6:30 ` KOSAKI Motohiro
2008-12-03 5:26 ` [PATCH] vmscan: improve reclaim throuput to bail out patch KOSAKI Motohiro
2008-12-03 5:26 ` KOSAKI Motohiro
2008-12-03 13:46 ` Rik van Riel [this message]
2008-12-03 13:46 ` Rik van Riel
2008-12-03 15:12 ` KOSAKI Motohiro
2008-12-03 15:12 ` KOSAKI Motohiro
2008-12-04 1:28 ` [PATCH] vmscan: improve reclaim throuput to bail out patch take2 KOSAKI Motohiro
2008-12-04 1:28 ` KOSAKI Motohiro
2008-12-04 4:20 ` MinChan Kim
2008-12-04 4:20 ` MinChan Kim
2008-12-04 5:04 ` KOSAKI Motohiro
2008-12-04 5:04 ` KOSAKI Motohiro
2008-12-07 3:28 ` Andrew Morton
2008-12-07 3:28 ` Andrew Morton
2008-12-08 2:49 ` KOSAKI Motohiro
2008-12-08 2:49 ` KOSAKI Motohiro
2008-12-01 13:40 ` [PATCH] vmscan: bail out of page reclaim after swap_cluster_max pages Christoph Lameter
2008-12-01 13:40 ` Christoph Lameter
2008-11-26 2:24 ` KOSAKI Motohiro
2008-11-26 2:24 ` KOSAKI Motohiro
2008-11-27 17:36 ` [rfc] vmscan: serialize aggressive reclaimers Johannes Weiner
2008-11-27 17:36 ` Johannes Weiner
2008-11-29 7:46 ` KOSAKI Motohiro
2008-11-29 7:46 ` KOSAKI Motohiro
2008-11-29 15:39 ` Johannes Weiner
2008-11-29 15:39 ` Johannes Weiner
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=49368DAF.9060206@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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.