Displaying 6 results from an estimated 6 matches for "1041,43".
2016 Mar 12
1
[PATCH v1 13/19] zsmalloc: factor page chain functionality out
...page(struct size_class *class, gfp_t flags)
> {
> - int i, error;
> + int i;
> struct page *first_page = NULL, *uninitialized_var(prev_page);
> + struct page *pages[ZS_MAX_PAGES_PER_ZSPAGE];
>
> /*
> * Allocate individual pages and link them together as:
> @@ -1041,43 +1074,23 @@ static struct page *alloc_zspage(struct size_class *class, gfp_t flags)
*uninitialized_var(prev_page) in alloc_zspage is not in use more.
> * (i.e. no other sub-page has this flag set) and PG_private_2 to
> * identify the last page.
> */
> - error = -ENOMEM...
2016 Mar 12
1
[PATCH v1 13/19] zsmalloc: factor page chain functionality out
...page(struct size_class *class, gfp_t flags)
> {
> - int i, error;
> + int i;
> struct page *first_page = NULL, *uninitialized_var(prev_page);
> + struct page *pages[ZS_MAX_PAGES_PER_ZSPAGE];
>
> /*
> * Allocate individual pages and link them together as:
> @@ -1041,43 +1074,23 @@ static struct page *alloc_zspage(struct size_class *class, gfp_t flags)
*uninitialized_var(prev_page) in alloc_zspage is not in use more.
> * (i.e. no other sub-page has this flag set) and PG_private_2 to
> * identify the last page.
> */
> - error = -ENOMEM...
2016 Mar 14
0
[PATCH v1 13/19] zsmalloc: factor page chain functionality out
...flags)
> > {
> >- int i, error;
> >+ int i;
> > struct page *first_page = NULL, *uninitialized_var(prev_page);
> >+ struct page *pages[ZS_MAX_PAGES_PER_ZSPAGE];
> >
> > /*
> > * Allocate individual pages and link them together as:
> >@@ -1041,43 +1074,23 @@ static struct page *alloc_zspage(struct size_class *class, gfp_t flags)
>
> *uninitialized_var(prev_page) in alloc_zspage is not in use more.
True.
It says why we should avoid uninitialized_var if possible.
If we didn't use uninitialized_var, compiler could warn about it...
2016 Mar 11
0
[PATCH v1 13/19] zsmalloc: factor page chain functionality out
...n size class
*/
static struct page *alloc_zspage(struct size_class *class, gfp_t flags)
{
- int i, error;
+ int i;
struct page *first_page = NULL, *uninitialized_var(prev_page);
+ struct page *pages[ZS_MAX_PAGES_PER_ZSPAGE];
/*
* Allocate individual pages and link them together as:
@@ -1041,43 +1074,23 @@ static struct page *alloc_zspage(struct size_class *class, gfp_t flags)
* (i.e. no other sub-page has this flag set) and PG_private_2 to
* identify the last page.
*/
- error = -ENOMEM;
for (i = 0; i < class->pages_per_zspage; i++) {
struct page *page;
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.