[PATCH] Documentation/trace/postprocess/trace-pagealloc-postprocess.pl: fix the traceevent regex

2014-02-28 Thread vinayakm . list
From: Vinayak Menon The script fails, when irq, preempt and lockdep fields (field 3 below) are printed in the trace output. Example entry: worker/0:0-4 [000] ...1 1155.972338: mm_page_alloc: Signed-off-by: Vinayak Menon --- .../postprocess/trace-pagealloc-postprocess.pl |8

[PATCH] Documentation/trace/postprocess/trace-pagealloc-postprocess.pl: fix the traceevent regex

2014-02-28 Thread vinayakm . list
From: Vinayak Menon vinayakm.l...@gmail.com The script fails, when irq, preempt and lockdep fields (field 3 below) are printed in the trace output. Example entry: worker/0:0-4 [000] ...1 1155.972338: mm_page_alloc: Signed-off-by: Vinayak Menon vinayakm.l...@gmail.com ---

[PATCH v3] staging: android: lowmemorykiller: neglect swap cached pages in other_file

2014-02-26 Thread vinayakm . list
From: Vinayak Menon With ZRAM enabled it is observed that lowmemory killer doesn't trigger properly. swap cached pages are accounted in NR_FILE, and lowmemorykiller considers this as reclaimable and adds to other_file. But these pages can't be reclaimed unless lowmemorykiller triggers. So

[PATCH] staging: android: lowmemorykiller: neglect swap cached pages in other_file

2014-02-26 Thread vinayakm . list
From: Vinayak Menon With ZRAM enabled it is observed that lowmemory killer doesn't trigger properly. swap cached pages are accounted in NR_FILE, and lowmemorykiller considers this as reclaimable and adds to other_file. But these pages can't be reclaimed unless lowmemorykiller triggers. So

[PATCH] staging: android: lowmemorykiller: neglect swap cached pages in other_file

2014-02-26 Thread vinayakm . list
From: Vinayak Menon With ZRAM enabled it is observed that lowmemory killer doesn't trigger properly. swap cached pages are accounted in NR_FILE, and lowmemorykiller considers this as reclaimable and adds to other_file. But these pages can't be reclaimed unless lowmemorykiller triggers. So

[PATCH] staging: android: lowmemorykiller: neglect swap cached pages in other_file

2014-02-26 Thread vinayakm . list
From: Vinayak Menon vinayakm.l...@gmail.com With ZRAM enabled it is observed that lowmemory killer doesn't trigger properly. swap cached pages are accounted in NR_FILE, and lowmemorykiller considers this as reclaimable and adds to other_file. But these pages can't be reclaimed unless

[PATCH] staging: android: lowmemorykiller: neglect swap cached pages in other_file

2014-02-26 Thread vinayakm . list
From: Vinayak Menon vinayakm.l...@gmail.com With ZRAM enabled it is observed that lowmemory killer doesn't trigger properly. swap cached pages are accounted in NR_FILE, and lowmemorykiller considers this as reclaimable and adds to other_file. But these pages can't be reclaimed unless

[PATCH v3] staging: android: lowmemorykiller: neglect swap cached pages in other_file

2014-02-26 Thread vinayakm . list
From: Vinayak Menon vinayakm.l...@gmail.com With ZRAM enabled it is observed that lowmemory killer doesn't trigger properly. swap cached pages are accounted in NR_FILE, and lowmemorykiller considers this as reclaimable and adds to other_file. But these pages can't be reclaimed unless

[PATCH] vmscan: tracing: Fix the traceevent regex

2013-12-11 Thread vinayakm . list
From: Vinayak Menon When irq, preempt and lockdep fields are printed (field 3 in the e.g. below) in the trace output, the script fails. An e.g. entry. kswapd0-610 [000] ...1 158.112152: mm_vmscan_kswapd_wake: nid=0 order=0 Signed-off-by: Vinayak Menon ---

[PATCH] vmscan: tracing: Fix the traceevent regex

2013-12-11 Thread vinayakm . list
From: Vinayak Menon vinayakm.l...@gmail.com When irq, preempt and lockdep fields are printed (field 3 in the e.g. below) in the trace output, the script fails. An e.g. entry. kswapd0-610 [000] ...1 158.112152: mm_vmscan_kswapd_wake: nid=0 order=0 Signed-off-by: Vinayak Menon

[PATCH v2] mm: add an option to disable bounce

2013-04-22 Thread vinayakm . list
From: Vinayak Menon There are times when HIGHMEM is enabled, but we don't prefer CONFIG_BOUNCE to be enabled. CONFIG_BOUNCE can reduce the block device throughput, and this is not ideal for machines where we don't gain much by enabling it. So provide an option to deselect CONFIG_BOUNCE. The

[PATCH] mm: add an option to disable bounce

2013-04-22 Thread vinayakm . list
From: Vinayak Menon There are times when HIGHMEM is enabled, but we don't prefer CONFIG_BOUNCE to be enabled. CONFIG_BOUNCE can reduce the block device throughput, and this is not ideal for machines where we don't gain much by enabling it. So provide an option to deselect CONFIG_BOUNCE. The

[PATCH] mm: add an option to disable bounce

2013-04-22 Thread vinayakm . list
From: Vinayak Menon vinayakm.l...@gmail.com There are times when HIGHMEM is enabled, but we don't prefer CONFIG_BOUNCE to be enabled. CONFIG_BOUNCE can reduce the block device throughput, and this is not ideal for machines where we don't gain much by enabling it. So provide an option to deselect

[PATCH v2] mm: add an option to disable bounce

2013-04-22 Thread vinayakm . list
From: Vinayak Menon vinayakm.l...@gmail.com There are times when HIGHMEM is enabled, but we don't prefer CONFIG_BOUNCE to be enabled. CONFIG_BOUNCE can reduce the block device throughput, and this is not ideal for machines where we don't gain much by enabling it. So provide an option to deselect