search for: mr_memory_failur

Displaying 15 results from an estimated 15 matches for "mr_memory_failur".

Did you mean: mr_memory_failure
mm/hwpoison: fix wrong num_poisoned_pages account
2016 Apr 04
1
mm/hwpoison: fix wrong num_poisoned_pages account
...erence grabbed during > > > >+ * isolation. Otherwise, restore the page to LRU list unless we > > > >+ * want to retry. > > > >+ */ > > > >+ if (rc == MIGRATEPAGE_SUCCESS) { > > > >+ put_page(page); > > > > if (reason == MR_MEMORY_FAILURE) { > > > >- put_page(page); > > > > if (!test_set_page_hwpoison(page)) > > > > num_poisoned_pages_inc(); > > > >- } else > > > >+ } > > > > > > Hmm, I didn't notice it previously, or it's due to reb...
mm/hwpoison: fix wrong num_poisoned_pages account
2016 Apr 04
1
mm/hwpoison: fix wrong num_poisoned_pages account
...erence grabbed during > > > >+ * isolation. Otherwise, restore the page to LRU list unless we > > > >+ * want to retry. > > > >+ */ > > > >+ if (rc == MIGRATEPAGE_SUCCESS) { > > > >+ put_page(page); > > > > if (reason == MR_MEMORY_FAILURE) { > > > >- put_page(page); > > > > if (!test_set_page_hwpoison(page)) > > > > num_poisoned_pages_inc(); > > > >- } else > > > >+ } > > > > > > Hmm, I didn't notice it previously, or it's due to reb...
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
2016 Apr 01
2
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
...list */ > + } > + > + /* > + * If migration is successful, drop the reference grabbed during > + * isolation. Otherwise, restore the page to LRU list unless we > + * want to retry. > + */ > + if (rc == MIGRATEPAGE_SUCCESS) { > + put_page(page); > if (reason == MR_MEMORY_FAILURE) { > - put_page(page); > if (!test_set_page_hwpoison(page)) > num_poisoned_pages_inc(); > - } else > + } Hmm, I didn't notice it previously, or it's due to rebasing, but it seems that you restricted the memory failure handling (i.e. setting hwpoison) to MIG...
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
2016 Apr 01
2
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
...list */ > + } > + > + /* > + * If migration is successful, drop the reference grabbed during > + * isolation. Otherwise, restore the page to LRU list unless we > + * want to retry. > + */ > + if (rc == MIGRATEPAGE_SUCCESS) { > + put_page(page); > if (reason == MR_MEMORY_FAILURE) { > - put_page(page); > if (!test_set_page_hwpoison(page)) > num_poisoned_pages_inc(); > - } else > + } Hmm, I didn't notice it previously, or it's due to rebasing, but it seems that you restricted the memory failure handling (i.e. setting hwpoison) to MIG...
[PATCH v1 01/19] mm: use put_page to free page instead of putback_lru_page
2016 Mar 11
0
[PATCH v1 01/19] mm: use put_page to free page instead of putback_lru_page
...t-offlined page shouldn't go through lru cache list */ + } + + /* + * If migration is successful, drop the reference grabbed during + * isolation. Otherwise, restore the page to LRU list unless we + * want to retry. + */ + if (rc == MIGRATEPAGE_SUCCESS) { + put_page(page); if (reason == MR_MEMORY_FAILURE) { - put_page(page); if (!test_set_page_hwpoison(page)) num_poisoned_pages_inc(); - } else + } + } else { + if (rc != -EAGAIN) putback_lru_page(page); + if (put_new_page) + put_new_page(newpage, private); + else + put_page(newpage); } - /* - * If migration was not succ...
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
2016 Mar 30
0
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
...t-offlined page shouldn't go through lru cache list */ + } + + /* + * If migration is successful, drop the reference grabbed during + * isolation. Otherwise, restore the page to LRU list unless we + * want to retry. + */ + if (rc == MIGRATEPAGE_SUCCESS) { + put_page(page); if (reason == MR_MEMORY_FAILURE) { - put_page(page); if (!test_set_page_hwpoison(page)) num_poisoned_pages_inc(); - } else + } + } else { + if (rc != -EAGAIN) putback_lru_page(page); + if (put_new_page) + put_new_page(newpage, private); + else + put_page(newpage); } - /* - * If migration was not succ...
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
2016 Apr 04
0
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
...;+ /* > >+ * If migration is successful, drop the reference grabbed during > >+ * isolation. Otherwise, restore the page to LRU list unless we > >+ * want to retry. > >+ */ > >+ if (rc == MIGRATEPAGE_SUCCESS) { > >+ put_page(page); > > if (reason == MR_MEMORY_FAILURE) { > >- put_page(page); > > if (!test_set_page_hwpoison(page)) > > num_poisoned_pages_inc(); > >- } else > >+ } > > Hmm, I didn't notice it previously, or it's due to rebasing, but it > seems that you restricted the memory failure handli...
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
2016 Apr 04
2
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
...on is successful, drop the reference grabbed during > > >+ * isolation. Otherwise, restore the page to LRU list unless we > > >+ * want to retry. > > >+ */ > > >+ if (rc == MIGRATEPAGE_SUCCESS) { > > >+ put_page(page); > > > if (reason == MR_MEMORY_FAILURE) { > > >- put_page(page); > > > if (!test_set_page_hwpoison(page)) > > > num_poisoned_pages_inc(); > > >- } else > > >+ } > > > > Hmm, I didn't notice it previously, or it's due to rebasing, but it > > seems that...
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
2016 Apr 04
2
[PATCH v3 01/16] mm: use put_page to free page instead of putback_lru_page
...on is successful, drop the reference grabbed during > > >+ * isolation. Otherwise, restore the page to LRU list unless we > > >+ * want to retry. > > >+ */ > > >+ if (rc == MIGRATEPAGE_SUCCESS) { > > >+ put_page(page); > > > if (reason == MR_MEMORY_FAILURE) { > > >- put_page(page); > > > if (!test_set_page_hwpoison(page)) > > > num_poisoned_pages_inc(); > > >- } else > > >+ } > > > > Hmm, I didn't notice it previously, or it's due to rebasing, but it > > seems that...
[PATCH v3 00/16] Support non-lru page migration
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.
[PATCH v3 00/16] Support non-lru page migration
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.
[PATCH v1 00/19] Support non-lru page migration
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.
[PATCH v1 00/19] Support non-lru page migration
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.
[PATCH v2 00/18] Support non-lru page migration
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.
[PATCH v2 00/18] Support non-lru page migration
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.