From: Vincent Li <macli@brc.ubc.ca>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vincent Li <macli@brc.ubc.ca>,
kosaki.motohiro@jp.fujitsu.com, riel@redhat.com,
minchan.kim@gmail.com, fengguang.wu@intel.com,
linux-mm@kvack.org
Subject: Re: [RESEND][PATCH V1] mm/vsmcan: check shrink_active_list() sc->isolate_pages() return value.
Date: Fri, 4 Sep 2009 14:39:32 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0909041431370.32680@kernelhack.brc.ubc.ca> (raw)
In-Reply-To: <20090903154704.da62dd76.akpm@linux-foundation.org>
On Thu, 3 Sep 2009, Andrew Morton wrote:
> On Thu, 3 Sep 2009 15:02:58 -0700 (PDT)
> Vincent Li <macli@brc.ubc.ca> wrote:
>
> > On Thu, 3 Sep 2009, Andrew Morton wrote:
> >
> > > On Wed, 2 Sep 2009 16:49:25 -0700
> > > Vincent Li <macli@brc.ubc.ca> wrote:
> > >
> > > > If we can't isolate pages from LRU list, we don't have to account page movement, either.
> > > > Already, in commit 5343daceec, KOSAKI did it about shrink_inactive_list.
> > > >
> > > > This patch removes unnecessary overhead of page accounting
> > > > and locking in shrink_active_list as follow-up work of commit 5343daceec.
> > > >
> > > > Signed-off-by: Vincent Li <macli@brc.ubc.ca>
> > > > Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
> > > > Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > > > Reviewed-by: Wu Fengguang <fengguang.wu@intel.com>
> > > > Acked-by: Rik van Riel <riel@redhat.com>
> > > >
> > > > ---
> > > > mm/vmscan.c | 9 +++++++--
> > > > 1 files changed, 7 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > > > index 460a6f7..2d1c846 100644
> > > > --- a/mm/vmscan.c
> > > > +++ b/mm/vmscan.c
> > > > @@ -1319,9 +1319,12 @@ static void shrink_active_list(unsigned long nr_pages, struct zone *zone,
> > > > if (scanning_global_lru(sc)) {
> > > > zone->pages_scanned += pgscanned;
> > > > }
> > > > - reclaim_stat->recent_scanned[file] += nr_taken;
> > > > -
> > > > __count_zone_vm_events(PGREFILL, zone, pgscanned);
> > > > +
> > > > + if (nr_taken == 0)
> > > > + goto done;
> > > > +
> > > > + reclaim_stat->recent_scanned[file] += nr_taken;
> > > > if (file)
> > > > __mod_zone_page_state(zone, NR_ACTIVE_FILE, -nr_taken);
> > > > else
> > > > @@ -1383,6 +1386,8 @@ static void shrink_active_list(unsigned long nr_pages, struct zone *zone,
> > > > __mod_zone_page_state(zone, NR_ISOLATED_ANON + file, -nr_taken);
> > > > __mod_zone_page_state(zone, LRU_ACTIVE + file * LRU_FILE, nr_rotated);
> > > > __mod_zone_page_state(zone, LRU_BASE + file * LRU_FILE, nr_deactivated);
> > > > +
> > > > +done:
> > > > spin_unlock_irq(&zone->lru_lock);
> > > > }
> > >
> > > How do we know this patch is a net gain?
> > >
> > > IOW, with what frequency is `nr_taken' zero here?
> > >
> >
> > Actually, I have asked myself the same question, Anyway I can verify this,
> > Kim, KOSAKI?
>
> Put two counters in there.
>
> They could be ad-hoc displayed-in-/proc counters. Or ad-hoc additions
> to /proc/vmstat. Or you could dive into the tracing framework and use
> that. These patches in -mm:
>
> tracing-page-allocator-add-trace-events-for-page-allocation-and-page-freeing.patch
> tracing-page-allocator-add-trace-events-for-anti-fragmentation-falling-back-to-other-migratetypes.patch
> tracing-page-allocator-add-trace-event-for-page-traffic-related-to-the-buddy-lists.patch
> tracing-page-allocator-add-trace-event-for-page-traffic-related-to-the-buddy-lists-fix.patch
> tracing-page-allocator-add-a-postprocessing-script-for-page-allocator-related-ftrace-events.patch
> tracing-documentation-add-a-document-describing-how-to-do-some-performance-analysis-with-tracepoints.patch
> tracing-documentation-add-a-document-on-the-kmem-tracepoints.patch
>
>
> would be a suitable guide.
>
Ok, I followed the patches above to make following testing code:
---
diff --git a/include/trace/events/kmem.h b/include/trace/events/kmem.h
index eaf46bd..863820a 100644
--- a/include/trace/events/kmem.h
+++ b/include/trace/events/kmem.h
@@ -388,6 +388,24 @@ TRACE_EVENT(mm_page_alloc_extfrag,
__entry->alloc_migratetype == __entry->fallback_migratetype)
);
+TRACE_EVENT(mm_vmscan_isolate_pages,
+
+ TP_PROTO(int nr_taken_zeros),
+
+ TP_ARGS(nr_taken_zeros),
+
+ TP_STRUCT__entry(
+ __field(int, nr_taken_zeros)
+ ),
+
+ TP_fast_assign(
+ __entry->nr_taken_zeros = nr_taken_zeros;
+ ),
+
+ TP_printk("nr_taken_zeros=%d",
+ __entry->nr_taken_zeros)
+);
+
#endif /* _TRACE_KMEM_H */
/* This part must be outside protection */
diff --git a/mm/vmscan.c b/mm/vmscan.c
index ad93096..c2cf4dd 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -40,6 +40,7 @@
#include <linux/memcontrol.h>
#include <linux/delayacct.h>
#include <linux/sysctl.h>
+#include <trace/events/kmem.h>
#include <asm/tlbflush.h>
#include <asm/div64.h>
@@ -1306,6 +1307,7 @@ static void shrink_active_list(unsigned long nr_pages, struct zone *zone,
struct zone_reclaim_stat *reclaim_stat = get_reclaim_stat(zone, sc);
unsigned long nr_rotated = 0;
unsigned long nr_deactivated = 0;
+ int nr_taken_zeros = 0;
lru_add_drain();
spin_lock_irq(&zone->lru_lock);
@@ -1321,8 +1323,11 @@ static void shrink_active_list(unsigned long nr_pages, struct zone *zone,
}
__count_zone_vm_events(PGREFILL, zone, pgscanned);
- if (nr_taken == 0)
+ if (nr_taken == 0) {
+ nr_taken_zeros++;
+ trace_mm_vmscan_isolate_pages(nr_taken_zeros);
goto done;
+ }
reclaim_stat->recent_scanned[file] += nr_taken;
if (file)
Then I got test result with:
root@kernelhack:/usr/src/mmotm-0903# perf stat --repeat 5 -e \
kmem:mm_vmscan_isolate_pages hackbench 100
Running with 100*40 (== 4000) tasks.
Time: 52.736
Running with 100*40 (== 4000) tasks.
Time: 64.982
Running with 100*40 (== 4000) tasks.
Time: 56.866
Running with 100*40 (== 4000) tasks.
Time: 37.137
Running with 100*40 (== 4000) tasks.
Time: 48.415
Performance counter stats for 'hackbench 100' (5 runs):
14189 kmem:mm_vmscan_isolate_pages ( +- 9.084% )
52.680621973 seconds time elapsed ( +- 0.689% )
Is the testing patch written write? I don't understand what the number
14189 means? Does it make any sense?
>
> The way I used to do stuff like this is:
>
> int akpm1;
> int akpm2;
>
> ...
> if (nr_taken)
> akpm1++;
> else
> akpm2++;
>
> then inspect the values of akpm1 and akpm2 in the running kernel using kgdb.
>
>
>
Vincent Li
Biomedical Research Center
University of British Columbia
--
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:[~2009-09-04 21:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 23:49 Vincent Li
2009-09-03 21:06 ` Andrew Morton
2009-09-03 22:02 ` Vincent Li
2009-09-03 22:47 ` Andrew Morton
2009-09-04 21:39 ` Vincent Li [this message]
2009-09-04 23:53 ` Andrew Morton
2009-09-08 13:21 ` Mel Gorman
2009-09-08 22:39 ` Vincent Li
2009-09-08 23:27 ` Minchan Kim
2009-10-15 22:47 ` Vincent Li
2009-10-15 23:13 ` Vincent Li
2009-10-16 2:10 ` Minchan Kim
2009-10-16 2:20 ` Wu Fengguang
2009-10-16 3:05 ` KOSAKI Motohiro
2009-10-16 3:26 ` Vincent Li
2009-11-26 4:56 ` KOSAKI Motohiro
2009-09-09 9:59 ` Mel Gorman
2009-09-04 1:37 ` Minchan Kim
2009-09-04 2:01 ` Andrew Morton
2009-09-04 5:01 ` Vincent Li
2009-09-04 16:05 ` Vincent Li
2009-09-06 23:38 ` KOSAKI Motohiro
2009-09-08 18:32 ` Vincent Li
2009-09-08 23:47 ` KOSAKI Motohiro
2009-09-09 12:04 ` Johannes Weiner
2009-09-09 13:22 ` Minchan Kim
2009-09-22 21:02 ` Andrew Morton
2009-09-22 23:01 ` Vincent Li
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=alpine.DEB.2.00.0909041431370.32680@kernelhack.brc.ubc.ca \
--to=macli@brc.ubc.ca \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--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