Displaying 4 results from an estimated 4 matches for "kpf_baloon".
Did you mean:
kpf_balloon
2016 Apr 05
1
[PATCH v3 04/16] mm/balloon: use general movable page feature into balloon
...pcount) == PAGE_BALLOON_MAPCOUNT_VALUE
> + && PagePrivate2(page);
> +}
Hmm so you are now using PG_private_2 flag here, but it's not
documented. Also the only caller of PageBalloon() seems to be
stable_page_flags(). Which will now report all movable pages with
PG_private_2 as KPF_BALOON. Seems like an overkill and also not
reliable. Could it test e.g. page->mapping instead?
Or maybe if we manage to get rid of PAGE_MOVABLE_MAPCOUNT_VALUE, we can
keep PAGE_BALLOON_MAPCOUNT_VALUE to simply distinguish balloon pages for
stable_page_flags().
> @@ -1033,7 +1019,7 @@ static in...
2016 Apr 05
1
[PATCH v3 04/16] mm/balloon: use general movable page feature into balloon
...pcount) == PAGE_BALLOON_MAPCOUNT_VALUE
> + && PagePrivate2(page);
> +}
Hmm so you are now using PG_private_2 flag here, but it's not
documented. Also the only caller of PageBalloon() seems to be
stable_page_flags(). Which will now report all movable pages with
PG_private_2 as KPF_BALOON. Seems like an overkill and also not
reliable. Could it test e.g. page->mapping instead?
Or maybe if we manage to get rid of PAGE_MOVABLE_MAPCOUNT_VALUE, we can
keep PAGE_BALLOON_MAPCOUNT_VALUE to simply distinguish balloon pages for
stable_page_flags().
> @@ -1033,7 +1019,7 @@ static in...
2016 Mar 30
33
[PATCH v3 00/16] Support non-lru page migration
Recently, I got many reports about perfermance degradation
in embedded system(Android mobile phone, webOS TV and so on)
and failed to fork easily.
The problem was fragmentation caused by zram and GPU driver
pages. Their pages cannot be migrated so compaction cannot
work well, either so reclaimer ends up shrinking all of working
set pages. It made system very slow and even to fail to fork
easily.
2016 Mar 30
33
[PATCH v3 00/16] Support non-lru page migration
Recently, I got many reports about perfermance degradation
in embedded system(Android mobile phone, webOS TV and so on)
and failed to fork easily.
The problem was fragmentation caused by zram and GPU driver
pages. Their pages cannot be migrated so compaction cannot
work well, either so reclaimer ends up shrinking all of working
set pages. It made system very slow and even to fail to fork
easily.