On Tue, Jul 04, 2017 at 01:24:14PM +0200, Michal Hocko wrote:
> On Tue 04-07-17 16:04:52, zhouxianrong wrote:
> > every 2s i sample /proc/buddyinfo in the whole test process.
> >
> > the last about 90 samples were sampled after the test was done.
>
> I've tried to explain to you that numbers
On Tue, Jul 04, 2017 at 01:24:14PM +0200, Michal Hocko wrote:
> On Tue 04-07-17 16:04:52, zhouxianrong wrote:
> > every 2s i sample /proc/buddyinfo in the whole test process.
> >
> > the last about 90 samples were sampled after the test was done.
>
> I've tried to explain to you that numbers
On Tue 04-07-17 16:04:52, zhouxianrong wrote:
> every 2s i sample /proc/buddyinfo in the whole test process.
>
> the last about 90 samples were sampled after the test was done.
I've tried to explain to you that numbers without a proper testing
metodology and highlevel metrics you are interested
On Tue 04-07-17 16:04:52, zhouxianrong wrote:
> every 2s i sample /proc/buddyinfo in the whole test process.
>
> the last about 90 samples were sampled after the test was done.
I've tried to explain to you that numbers without a proper testing
metodology and highlevel metrics you are interested
every 2s i sample /proc/buddyinfo in the whole test process.
the last about 90 samples were sampled after the test was done.
Node 0, zone DMA
4706 2099838266 50 5 3 2 1 2 38
0395 1261211 57 6 1 0 0 0
every 2s i sample /proc/buddyinfo in the whole test process.
the last about 90 samples were sampled after the test was done.
Node 0, zone DMA
4706 2099838266 50 5 3 2 1 2 38
0395 1261211 57 6 1 0 0 0
i do the test again. after minutes i tell you the result.
On 2017/7/4 14:52, Michal Hocko wrote:
On Tue 04-07-17 09:21:00, zhouxianrong wrote:
the test was done as follows:
1. the environment is android 7.0 and kernel is 4.1 and managed memory is 3.5GB
There have been many changes in the
i do the test again. after minutes i tell you the result.
On 2017/7/4 14:52, Michal Hocko wrote:
On Tue 04-07-17 09:21:00, zhouxianrong wrote:
the test was done as follows:
1. the environment is android 7.0 and kernel is 4.1 and managed memory is 3.5GB
There have been many changes in the
On Tue 04-07-17 09:21:00, zhouxianrong wrote:
> the test was done as follows:
>
> 1. the environment is android 7.0 and kernel is 4.1 and managed memory is
> 3.5GB
There have been many changes in the compaction proper since than. Do you
see the same problem with the current upstream kernel?
>
On Tue 04-07-17 09:21:00, zhouxianrong wrote:
> the test was done as follows:
>
> 1. the environment is android 7.0 and kernel is 4.1 and managed memory is
> 3.5GB
There have been many changes in the compaction proper since than. Do you
see the same problem with the current upstream kernel?
>
the test was done as follows:
1. the environment is android 7.0 and kernel is 4.1 and managed memory is 3.5GB
2. every 4s startup one apk, total 100 more apks need to startup
3. after finishing step 2, sample buddyinfo once and get the result
On 2017/7/3 23:33, Michal Hocko wrote:
On Mon
the test was done as follows:
1. the environment is android 7.0 and kernel is 4.1 and managed memory is 3.5GB
2. every 4s startup one apk, total 100 more apks need to startup
3. after finishing step 2, sample buddyinfo once and get the result
On 2017/7/3 23:33, Michal Hocko wrote:
On Mon
On Mon 03-07-17 20:02:16, zhouxianrong wrote:
[...]
> from above i think after applying the patch the result is better.
You haven't described your testing methodology, nor the workload that was
tested. As such this data is completely meaningless.
--
Michal Hocko
SUSE Labs
On Mon 03-07-17 20:02:16, zhouxianrong wrote:
[...]
> from above i think after applying the patch the result is better.
You haven't described your testing methodology, nor the workload that was
tested. As such this data is completely meaningless.
--
Michal Hocko
SUSE Labs
On 2017/7/3 15:48, Michal Hocko wrote:
On Fri 30-06-17 19:25:41, zhouxianr...@huawei.com wrote:
From: zhouxianrong
when buddy is under fragment i find that still there are some pages
just like AFFA mode. A is allocated, F is free, AF is buddy pair for
oder n, FA is
On 2017/7/3 15:48, Michal Hocko wrote:
On Fri 30-06-17 19:25:41, zhouxianr...@huawei.com wrote:
From: zhouxianrong
when buddy is under fragment i find that still there are some pages
just like AFFA mode. A is allocated, F is free, AF is buddy pair for
oder n, FA is buddy pair for oder n
On 2017/7/3 15:48, Michal Hocko wrote:
On Fri 30-06-17 19:25:41, zhouxianr...@huawei.com wrote:
From: zhouxianrong
when buddy is under fragment i find that still there are some pages
just like AFFA mode. A is allocated, F is free, AF is buddy pair for
oder n, FA is
On 2017/7/3 15:48, Michal Hocko wrote:
On Fri 30-06-17 19:25:41, zhouxianr...@huawei.com wrote:
From: zhouxianrong
when buddy is under fragment i find that still there are some pages
just like AFFA mode. A is allocated, F is free, AF is buddy pair for
oder n, FA is buddy pair for oder n
On Fri 30-06-17 19:25:41, zhouxianr...@huawei.com wrote:
> From: zhouxianrong
>
> when buddy is under fragment i find that still there are some pages
> just like AFFA mode. A is allocated, F is free, AF is buddy pair for
> oder n, FA is buddy pair for oder n as well.
On Fri 30-06-17 19:25:41, zhouxianr...@huawei.com wrote:
> From: zhouxianrong
>
> when buddy is under fragment i find that still there are some pages
> just like AFFA mode. A is allocated, F is free, AF is buddy pair for
> oder n, FA is buddy pair for oder n as well.
Could you quantify how
From: zhouxianrong
when buddy is under fragment i find that still there are some pages
just like AFFA mode. A is allocated, F is free, AF is buddy pair for
oder n, FA is buddy pair for oder n as well. I want to compse the
FF as oder n
From: zhouxianrong
when buddy is under fragment i find that still there are some pages
just like AFFA mode. A is allocated, F is free, AF is buddy pair for
oder n, FA is buddy pair for oder n as well. I want to compse the
FF as oder n + 1 and align to n other
From: z00281421
Signed-off-by: z00281421
---
include/linux/gfp.h |8 +-
include/linux/mmzone.h |2 +
include/linux/page-flags.h |9 ++
include/linux/thread_info.h |5 +-
mm/compaction.c |
From: z00281421
Signed-off-by: z00281421
---
include/linux/gfp.h |8 +-
include/linux/mmzone.h |2 +
include/linux/page-flags.h |9 ++
include/linux/thread_info.h |5 +-
mm/compaction.c | 17
mm/internal.h |7 ++
24 matches
Mail list logo