Displaying 13 results from an estimated 13 matches for "prev_pag".
Did you mean:
prev_page
2016 Mar 12
1
[PATCH v1 13/19] zsmalloc: factor page chain functionality out
...page;
> @@ -1022,13 +1024,44 @@ static void init_zspage(struct size_class *class, struct page *first_page)
> set_freeobj(first_page, 0);
> }
>
> +static void create_page_chain(struct page *pages[], int nr_pages)
> +{
> + int i;
> + struct page *page;
> + struct page *prev_page = NULL;
> + struct page *first_page = NULL;
> +
> + for (i = 0; i < nr_pages; i++) {
> + page = pages[i];
> +
> + INIT_LIST_HEAD(&page->lru);
> + if (i == 0) {
> + SetPagePrivate(page);
> + set_page_private(page, 0);
> + first_page = page;
> + }...
2016 Mar 12
1
[PATCH v1 13/19] zsmalloc: factor page chain functionality out
...page;
> @@ -1022,13 +1024,44 @@ static void init_zspage(struct size_class *class, struct page *first_page)
> set_freeobj(first_page, 0);
> }
>
> +static void create_page_chain(struct page *pages[], int nr_pages)
> +{
> + int i;
> + struct page *page;
> + struct page *prev_page = NULL;
> + struct page *first_page = NULL;
> +
> + for (i = 0; i < nr_pages; i++) {
> + page = pages[i];
> +
> + INIT_LIST_HEAD(&page->lru);
> + if (i == 0) {
> + SetPagePrivate(page);
> + set_page_private(page, 0);
> + first_page = page;
> + }...
2016 Mar 11
0
[PATCH v1 13/19] zsmalloc: factor page chain functionality out
...0);
while (page) {
struct page *next_page;
@@ -1022,13 +1024,44 @@ static void init_zspage(struct size_class *class, struct page *first_page)
set_freeobj(first_page, 0);
}
+static void create_page_chain(struct page *pages[], int nr_pages)
+{
+ int i;
+ struct page *page;
+ struct page *prev_page = NULL;
+ struct page *first_page = NULL;
+
+ for (i = 0; i < nr_pages; i++) {
+ page = pages[i];
+
+ INIT_LIST_HEAD(&page->lru);
+ if (i == 0) {
+ SetPagePrivate(page);
+ set_page_private(page, 0);
+ first_page = page;
+ }
+
+ if (i == 1)
+ set_page_private(first_page, (uns...
2016 Mar 30
0
[PATCH v3 10/16] zsmalloc: factor page chain functionality out
...0);
while (page) {
struct page *next_page;
@@ -1026,13 +1028,44 @@ static void init_zspage(struct size_class *class, struct page *first_page)
set_freeobj(first_page, 0);
}
+static void create_page_chain(struct page *pages[], int nr_pages)
+{
+ int i;
+ struct page *page;
+ struct page *prev_page = NULL;
+ struct page *first_page = NULL;
+
+ for (i = 0; i < nr_pages; i++) {
+ page = pages[i];
+
+ INIT_LIST_HEAD(&page->lru);
+ if (i == 0) {
+ SetPagePrivate(page);
+ set_page_private(page, 0);
+ first_page = page;
+ }
+
+ if (i == 1)
+ set_page_private(first_page, (uns...
2016 Mar 14
0
[PATCH v1 13/19] zsmalloc: factor page chain functionality out
...@ static void init_zspage(struct size_class *class, struct page *first_page)
> > set_freeobj(first_page, 0);
> > }
> >
> >+static void create_page_chain(struct page *pages[], int nr_pages)
> >+{
> >+ int i;
> >+ struct page *page;
> >+ struct page *prev_page = NULL;
> >+ struct page *first_page = NULL;
> >+
> >+ for (i = 0; i < nr_pages; i++) {
> >+ page = pages[i];
> >+
> >+ INIT_LIST_HEAD(&page->lru);
> >+ if (i == 0) {
> >+ SetPagePrivate(page);
> >+ set_page_private(page, 0);
&...
2006 Feb 15
9
newbie-> help understanding "magic" behavior
...html.
The only definition of the ''next'' method I can find is within the
''paginator'' class, yet I am not invoking that class as far as I can
tell. So there''s no problem with next per se, but trying to do the
opposite (in my mind, anyway) by setting
@prev_page = Content.find(params["id".previous (and many, many other
attempts, like prev, or id -1, just to be utterly hacky)
Only gets me errors, and googling has so far not yielded the solution.
Any suggestions? Am I even trying to do this in the Right Place? The
book has been ordered, befor...
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.
2016 Mar 11
0
[PATCH v1 07/19] zsmalloc: reordering function parameter
...id init_zspage(struct page *first_page, struct size_class *class)
+static void init_zspage(struct size_class *class, struct page *first_page)
{
unsigned long off = 0;
struct page *page = first_page;
@@ -998,7 +1000,7 @@ static struct page *alloc_zspage(struct size_class *class, gfp_t flags)
prev_page = page;
}
- init_zspage(first_page, class);
+ init_zspage(class, first_page);
first_page->freelist = location_to_obj(first_page, 0);
/* Maximum number of objects we can store in this zspage */
@@ -1345,8 +1347,8 @@ void zs_unmap_object(struct zs_pool *pool, unsigned long handle)
}
E...
2016 Mar 21
22
[PATCH v2 00/18] 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 21
22
[PATCH v2 00/18] 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.
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.