Currently vmstat considers only the freepages present in the buddy freelists
of the page allocator. But with the newly introduced region allocator in
place, freepages could be present in the region allocator as well. So teach
vmstat to take them into consideration when reporting free memory.

Signed-off-by: Srivatsa S. Bhat <srivatsa.b...@linux.vnet.ibm.com>
---

 mm/vmstat.c |    8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/mm/vmstat.c b/mm/vmstat.c
index 924babc..8cb7a10 100644
--- a/mm/vmstat.c
+++ b/mm/vmstat.c
@@ -829,6 +829,8 @@ static void frag_show_print(struct seq_file *m, pg_data_t 
*pgdat,
 {
        int i, order, t;
        struct free_area *area;
+       struct free_area_region *reg_area;
+       struct region_allocator *reg_alloc;
 
        seq_printf(m, "Node %d, zone %8s \n", pgdat->node_id, zone->name);
 
@@ -845,6 +847,12 @@ static void frag_show_print(struct seq_file *m, pg_data_t 
*pgdat,
                                nr_free +=
                                        area->free_list[t].mr_list[i].nr_free;
                        }
+
+                       /* Add up freepages in the region allocator as well */
+                       reg_alloc = &zone->region_allocator;
+                       reg_area = &reg_alloc->region[i].region_area[order];
+                       nr_free += reg_area->nr_free;
+
                        seq_printf(m, "%6lu ", nr_free);
                }
                seq_putc(m, '\n');

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to