Displaying 6 results from an estimated 6 matches for "622,21".
Did you mean:
22,21
2016 Mar 12
1
[PATCH v1 09/19] zsmalloc: keep max_object in size_class
...s in a fullness group.
> * page->mapping: class index and fullness group of the zspage
> @@ -211,6 +209,7 @@ struct size_class {
> * of ZS_ALIGN.
> */
> int size;
> + int objs_per_zspage;
> unsigned int index;
>
> struct zs_size_stat stats;
> @@ -622,21 +621,22 @@ static inline void zs_pool_stat_destroy(struct zs_pool *pool)
> * the pool (not yet implemented). This function returns fullness
> * status of the given page.
> */
> -static enum fullness_group get_fullness_group(struct page *first_page)
> +static enum fullness...
2016 Mar 12
1
[PATCH v1 09/19] zsmalloc: keep max_object in size_class
...s in a fullness group.
> * page->mapping: class index and fullness group of the zspage
> @@ -211,6 +209,7 @@ struct size_class {
> * of ZS_ALIGN.
> */
> int size;
> + int objs_per_zspage;
> unsigned int index;
>
> struct zs_size_stat stats;
> @@ -622,21 +621,22 @@ static inline void zs_pool_stat_destroy(struct zs_pool *pool)
> * the pool (not yet implemented). This function returns fullness
> * status of the given page.
> */
> -static enum fullness_group get_fullness_group(struct page *first_page)
> +static enum fullness...
2016 Mar 11
0
[PATCH v1 09/19] zsmalloc: keep max_object in size_class
...various zspages.
* Basically forming list of zspages in a fullness group.
* page->mapping: class index and fullness group of the zspage
@@ -211,6 +209,7 @@ struct size_class {
* of ZS_ALIGN.
*/
int size;
+ int objs_per_zspage;
unsigned int index;
struct zs_size_stat stats;
@@ -622,21 +621,22 @@ static inline void zs_pool_stat_destroy(struct zs_pool *pool)
* the pool (not yet implemented). This function returns fullness
* status of the given page.
*/
-static enum fullness_group get_fullness_group(struct page *first_page)
+static enum fullness_group get_fullness_group(st...
2016 Mar 14
0
[PATCH v1 09/19] zsmalloc: keep max_object in size_class
...->mapping: class index and fullness group of the zspage
> >@@ -211,6 +209,7 @@ struct size_class {
> > * of ZS_ALIGN.
> > */
> > int size;
> >+ int objs_per_zspage;
> > unsigned int index;
> >
> > struct zs_size_stat stats;
> >@@ -622,21 +621,22 @@ static inline void zs_pool_stat_destroy(struct zs_pool *pool)
> > * the pool (not yet implemented). This function returns fullness
> > * status of the given page.
> > */
> >-static enum fullness_group get_fullness_group(struct page *first_page)
> >+...
2016 Mar 11
31
[PATCH v1 00/19] 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 11
31
[PATCH v1 00/19] 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.