From: San Mehat <san@google.com>
To: "Arve Hjønnevåg" <arve@android.com>
Cc: "Minchan Kim" <minchan.kim@gmail.com>,
"Alejandro Riveira Fernández" <ariveira@gmail.com>,
swetland@google.com, linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: android-kernel memory reclaim x20 boost?
Date: Wed, 18 Aug 2010 18:04:03 -0700 [thread overview]
Message-ID: <AANLkTinjKK_jKm04BNmTRwq5uW8ainDcJHOXCGCmOXuD@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimqzQHtSo5f41ze4JEznGCjMNTC_1DPgc21JYT0@mail.gmail.com>
On Wed, Aug 18, 2010 at 6:01 PM, Arve Hjønnevåg <arve@android.com> wrote:
> On Wed, Aug 18, 2010 at 5:54 PM, Minchan Kim <minchan.kim@gmail.com> wrote:
>> On Thu, Aug 19, 2010 at 12:26 AM, Alejandro Riveira Fernández
>> <ariveira@gmail.com> wrote:
>>> El Thu, 19 Aug 2010 00:18:57 +0900
>>> Minchan Kim <minchan.kim@gmail.com> escribió:
>>>
>>>> Hello Android forks,
>>> [ ... ]
>>>>
>>>> I saw the advertisement phrase in this[1].
>>>>
>>>> "Kernel Memory Management Boost: Improved memory reclaim by up to 20x,
>>>> which results in faster app switching and smoother performance
>>>> on memory-constrained devices."
>>>>
>>>> But I can't find any code for it in android kernel git tree.
>>>
>>> Maybe the enhancements are on the Dalvik VM (shooting in the dark here)
>>
>> Thanks.
>> Android guys! Could you confirm this?
>>
>
> It is more likely referring to this change:
>
There are other changes after the one mentioned that remove the
requirement for CONFIG_PROFILING
(and the subsequent task_struct leak that was caused by it)
-san
> Author: San Mehat <san@google.com>
> Date: Wed May 5 11:38:42 2010 -0700
>
> staging: android: lowmemkiller: Substantially reduce overhead during reclaim
>
> This patch optimizes lowmemkiller to not do any work when it has
> an outstanding
> kill-request. This greatly reduces the pressure on the task_list lock
> (improving interactivity), as well as improving the vmscan performance
> when under heavy memory pressure (by up to 20x in tests).
>
> Note: For this enhancement to work, you need CONFIG_PROFILING
>
> Signed-off-by: San Mehat <san@google.com>
>
>
> --
> Arve Hjønnevåg
>
--
San Mehat | Staff Software Engineer | Infrastructure | Google Inc.
415.366.6172 (san@google.com)
--
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:[~2010-08-19 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 15:18 Minchan Kim
2010-08-18 15:26 ` Alejandro Riveira Fernández
2010-08-19 0:54 ` Minchan Kim
2010-08-19 1:01 ` Arve Hjønnevåg
2010-08-19 1:04 ` San Mehat [this message]
2010-08-19 1:53 ` Minchan Kim
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=AANLkTinjKK_jKm04BNmTRwq5uW8ainDcJHOXCGCmOXuD@mail.gmail.com \
--to=san@google.com \
--cc=ariveira@gmail.com \
--cc=arve@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=swetland@google.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