Re: [PATCH][for -mm] fix accounting in vmscan.c for memory controller

Previous thread: [patch 1/1] Writeback fix for concurrent large and small file writes. by Michael Rubin on Monday, December 10, 2007 - 10:02 pm. (4 messages)

Next thread: [DOC][for -mm] update Documentation/controller/memory.txt by KAMEZAWA Hiroyuki on Monday, December 10, 2007 - 11:03 pm. (2 messages)
To: Andrew Morton <akpm@...>
Cc: balbir@linux.vnet.ibm.com <balbir@...>, yamamoto@valinux.co.jp <yamamoto@...>, LKML <linux-kernel@...>, linux-mm@kvack.org <linux-mm@...>, riel@redhat.com <riel@...>
Date: Monday, December 10, 2007 - 10:26 pm

Without this, ALLOCSTALL and PGSCAN_DIRECT increases too much unless
there is no memory shortage.

against 2.6.24-rc4-mm1.

-Kame

==
Some amount of accounting is done while page reclaiming.

Now, there are 2 types of page reclaim (if memory controller is used)
- global: shortage of (global) pages.
- under cgroup: use up to limit.

I think 2 accountings, ALLOCSTALL and DIRECT should be accounted only under
global lru scan. They are accounted against memory shortage at alloc_pages().

Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>

mm/vmscan.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)

Index: linux-2.6.24-rc4-mm1/mm/vmscan.c
===================================================================
--- linux-2.6.24-rc4-mm1.orig/mm/vmscan.c
+++ linux-2.6.24-rc4-mm1/mm/vmscan.c
@@ -896,8 +896,9 @@ static unsigned long shrink_inactive_lis
if (current_is_kswapd()) {
__count_zone_vm_events(PGSCAN_KSWAPD, zone, nr_scan);
__count_vm_events(KSWAPD_STEAL, nr_freed);
- } else
+ } else if (scan_global_lru(sc))
__count_zone_vm_events(PGSCAN_DIRECT, zone, nr_scan);
+
__count_zone_vm_events(PGSTEAL, zone, nr_freed);

if (nr_taken == 0)
@@ -1333,7 +1334,8 @@ static unsigned long do_try_to_free_page
unsigned long lru_pages = 0;
int i;

- count_vm_event(ALLOCSTALL);
+ if (scan_global_lru(sc))
+ count_vm_event(ALLOCSTALL);
/*
* mem_cgroup will not do shrink_slab.
*/

--

To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...>
Cc: Andrew Morton <akpm@...>, balbir@linux.vnet.ibm.com <balbir@...>, yamamoto@valinux.co.jp <yamamoto@...>, LKML <linux-kernel@...>, linux-mm@kvack.org <linux-mm@...>, riel@redhat.com <riel@...>
Date: Tuesday, December 11, 2007 - 7:24 am

On Tue, 11 Dec 2007 11:26:44 +0900
Sorry,

Without this, ALLOCSTALL and PGSCAN_DIRECT increases too much even if
^^^^^^^
there is no memory shortage.

--

To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...>
Cc: Andrew Morton <akpm@...>, yamamoto@valinux.co.jp <yamamoto@...>, LKML <linux-kernel@...>, linux-mm@kvack.org <linux-mm@...>, riel@redhat.com <riel@...>
Date: Tuesday, December 11, 2007 - 1:14 am

Looks good to me.

Acked-by: Balbir Singh <balbir@linux.vnet.ibm.com>

TODO:

1. Should we have vm_events for the memory controller as well?
May be in the longer term

--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--

To: <balbir@...>
Cc: Andrew Morton <akpm@...>, yamamoto@valinux.co.jp <yamamoto@...>, LKML <linux-kernel@...>, linux-mm@kvack.org <linux-mm@...>, riel@redhat.com <riel@...>
Date: Tuesday, December 11, 2007 - 1:29 am

On Tue, 11 Dec 2007 10:44:36 +0530

ALLOC_STALL is recoreded as failcnt, I think.
I think DIRECT can be accoutned easily.

But I'm not in hurry very much, because all reclaimation is DIRECT, now.
After we implement background reclaim, we should consider it.

Thanks,
-Kame

--

To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...>
Cc: Andrew Morton <akpm@...>, yamamoto@valinux.co.jp <yamamoto@...>, LKML <linux-kernel@...>, linux-mm@kvack.org <linux-mm@...>, riel@redhat.com <riel@...>
Date: Tuesday, December 11, 2007 - 1:36 am

Thanks for clarifying

--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--

Previous thread: [patch 1/1] Writeback fix for concurrent large and small file writes. by Michael Rubin on Monday, December 10, 2007 - 10:02 pm. (4 messages)

Next thread: [DOC][for -mm] update Documentation/controller/memory.txt by KAMEZAWA Hiroyuki on Monday, December 10, 2007 - 11:03 pm. (2 messages)