Updates for LowMemoryKiller
lowmemorykiller: make default lowmemorykiller debug message useful

lowmemorykiller debug messages are inscrutable and mostly useful
for debugging the lowmemorykiller, not explaining why a process
was killed.  Make the messages more useful by prefixing them
with "lowmemorykiller: " and explaining in more readable terms
what was killed, who it was killed for, and why it was killed.

The messages now look like:
[   76.997631] lowmemorykiller: Killing 'droid.gallery3d' (2172), adj 1000,
[   76.997635]    to free 27436kB on behalf of 'kswapd0' (29) because
[   76.997638]    cache 122624kB is below limit 122880kB for oom_score_adj 1000
[   76.997641]    Free memory is -53356kB above reserved

A negative number for free memory above reserved means some of the
reserved memory has been used and is being regenerated by kswapd,
which is likely what called the shrinkers.

Change-Id: I1fe983381e73e124b90aa5d91cb66e55eaca390f
Signed-off-by: Colin Cross <ccross@android.com>

Conflicts:
	drivers/staging/android/lowmemorykiller.c
LOW MEM KILL: Sync with 3.10.y and removed auto AUTODETECT_OOM_ADJ_VALUES
seems that this code is no longer working as should with new updates to OOM
and MM

now tested and system working good!

>.4dd invoked oom-killer: gfp_mask=0x200d2, order=0, oom_adj=0, oom_score_adj=0
>.3Out of memory (oom_kill_allocating_task): Kill process 21093 (dd) score 0 or sacrifice child
>.3Killed process 21093 (dd) total-vm:1892kB, anon-rss:48kB, file-rss:152kB
>.4Thread-247 invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=9, oom_score_adj=529
>.3Out of memory (oom_kill_allocating_task): Kill process 18032 (Thread-247) score 0 or sacrifice child
>.3Killed process 18032 (Thread-247) total-vm:380180kB, anon-rss:69940kB, file-rss:56kB
>.4WifiStateMachin invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=-16, oom_score_adj=-941
>.3Out of memory (oom_kill_allocating_task): Kill process 6964 (WifiStateMachin) score 0 or sacrifice child
>.3Killed process 6964 (WifiStateMachin) total-vm:448552kB, anon-rss:42568kB, file-rss:44kB
>.4FMOD stream thr invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=7, oom_score_adj=411
>.3Out of memory (oom_kill_allocating_task): Kill process 19095 (FMOD stream thr) score 0 or sacrifice child
>.3Killed process 19095 (FMOD stream thr) total-vm:422068kB, anon-rss:79032kB, file-rss:36kB

did dd to create 210MB file! and system survived the test!
when reached low mem.

Unmerged:

	arch/arm/configs/dorimanx_defconfig
mm: writeback: every 500ms the writeback daemon kicks in and flushes …
…the dirty pages into disk. Thats not very pleasant for performance and *maybe* battery. This patch disables the writeback function while the screen is on, and enables it back when the screen is off to flush all the dirty pages. In my real world usage testing I notice a slight bump in smoothness and performance while using the device.

Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
Signed-off-by: erik96 <ariesrik96@gmail.com>
Merge branch 'jb-3.0_phenom' of github.com:erik96/samsung-kernel-msm7x30 into jb-3.0_phenom