search for: isolate_lru_page

...ed. > > Yes, while I read the code, I had same question. I think the releasing > refcount is for get_any_page. As the other callers of page migration do, soft_offline_page expects the migration source page to be freed at this put_page() (no pin remains.) The refcount released here is from isolate_lru_page() in __soft_offline_page(). (the pin by get_any_page is released by put_hwpoison_page just after it.) .. yes, doing something just after freeing page looks weird, but that's how PageHWPoison flag works. IOW, many other page flags are maintained only during one "allocate-free" life sp...

...ed. > > Yes, while I read the code, I had same question. I think the releasing > refcount is for get_any_page. As the other callers of page migration do, soft_offline_page expects the migration source page to be freed at this put_page() (no pin remains.) The refcount released here is from isolate_lru_page() in __soft_offline_page(). (the pin by get_any_page is released by put_hwpoison_page just after it.) .. yes, doing something just after freeing page looks weird, but that's how PageHWPoison flag works. IOW, many other page flags are maintained only during one "allocate-free" life sp...

...ame question. I think the releasing > >> refcount is for get_any_page. > > > > As the other callers of page migration do, soft_offline_page expects the > > migration source page to be freed at this put_page() (no pin remains.) > > The refcount released here is from isolate_lru_page() in __soft_offline_page(). > > (the pin by get_any_page is released by put_hwpoison_page just after it.) > > > > .. yes, doing something just after freeing page looks weird, but that's > > how PageHWPoison flag works. IOW, many other page flags are maintained > >...

...ame question. I think the releasing > >> refcount is for get_any_page. > > > > As the other callers of page migration do, soft_offline_page expects the > > migration source page to be freed at this put_page() (no pin remains.) > > The refcount released here is from isolate_lru_page() in __soft_offline_page(). > > (the pin by get_any_page is released by put_hwpoison_page just after it.) > > > > .. yes, doing something just after freeing page looks weird, but that's > > how PageHWPoison flag works. IOW, many other page flags are maintained > >...

...I read the code, I had same question. I think the releasing >> refcount is for get_any_page. > > As the other callers of page migration do, soft_offline_page expects the > migration source page to be freed at this put_page() (no pin remains.) > The refcount released here is from isolate_lru_page() in __soft_offline_page(). > (the pin by get_any_page is released by put_hwpoison_page just after it.) > > .. yes, doing something just after freeing page looks weird, but that's > how PageHWPoison flag works. IOW, many other page flags are maintained > only during one "al...

...I read the code, I had same question. I think the releasing > > refcount is for get_any_page. > > As the other callers of page migration do, soft_offline_page expects the > migration source page to be freed at this put_page() (no pin remains.) > The refcount released here is from isolate_lru_page() in __soft_offline_page(). > (the pin by get_any_page is released by put_hwpoison_page just after it.) > > .. yes, doing something just after freeing page looks weird, but that's > how PageHWPoison flag works. IOW, many other page flags are maintained > only during one "al...

...I read the code, I had same question. I think the releasing > > refcount is for get_any_page. > > As the other callers of page migration do, soft_offline_page expects the > migration source page to be freed at this put_page() (no pin remains.) > The refcount released here is from isolate_lru_page() in __soft_offline_page(). > (the pin by get_any_page is released by put_hwpoison_page just after it.) > > .. yes, doing something just after freeing page looks weird, but that's > how PageHWPoison flag works. IOW, many other page flags are maintained > only during one "al...

...I think the releasing >>>> refcount is for get_any_page. >>> >>> As the other callers of page migration do, soft_offline_page expects the >>> migration source page to be freed at this put_page() (no pin remains.) >>> The refcount released here is from isolate_lru_page() in __soft_offline_page(). >>> (the pin by get_any_page is released by put_hwpoison_page just after it.) >>> >>> .. yes, doing something just after freeing page looks weird, but that's >>> how PageHWPoison flag works. IOW, many other page flags are maintaine...

On 30/03/16 18:12, Minchan Kim wrote: > Procedure of page migration is as follows: > > First of all, it should isolate a page from LRU and try to > migrate the page. If it is successful, it releases the page > for freeing. Otherwise, it should put the page back to LRU > list. > > For LRU pages, we have used putback_lru_page for both freeing > and putback to LRU list.

On 30/03/16 18:12, Minchan Kim wrote: > Procedure of page migration is as follows: > > First of all, it should isolate a page from LRU and try to > migrate the page. If it is successful, it releases the page > for freeing. Otherwise, it should put the page back to LRU > list. > > For LRU pages, we have used putback_lru_page for both freeing > and putback to LRU list.

...; >>>> refcount is for get_any_page. > >>> > >>> As the other callers of page migration do, soft_offline_page expects the > >>> migration source page to be freed at this put_page() (no pin remains.) > >>> The refcount released here is from isolate_lru_page() in __soft_offline_page(). > >>> (the pin by get_any_page is released by put_hwpoison_page just after it.) > >>> > >>> .. yes, doing something just after freeing page looks weird, but that's > >>> how PageHWPoison flag works. IOW, many other page...

...; >>>> refcount is for get_any_page. > >>> > >>> As the other callers of page migration do, soft_offline_page expects the > >>> migration source page to be freed at this put_page() (no pin remains.) > >>> The refcount released here is from isolate_lru_page() in __soft_offline_page(). > >>> (the pin by get_any_page is released by put_hwpoison_page just after it.) > >>> > >>> .. yes, doing something just after freeing page looks weird, but that's > >>> how PageHWPoison flag works. IOW, many other page...

On 03/30/2016 09:12 AM, Minchan Kim wrote: > Procedure of page migration is as follows: > > First of all, it should isolate a page from LRU and try to > migrate the page. If it is successful, it releases the page > for freeing. Otherwise, it should put the page back to LRU > list. > > For LRU pages, we have used putback_lru_page for both freeing > and putback to LRU

On 03/30/2016 09:12 AM, Minchan Kim wrote: > Procedure of page migration is as follows: > > First of all, it should isolate a page from LRU and try to > migrate the page. If it is successful, it releases the page > for freeing. Otherwise, it should put the page back to LRU > list. > > For LRU pages, we have used putback_lru_page for both freeing > and putback to LRU

...VM_BUG_ON_PAGE(!((unsigned long)page->mapping & PAGE_MAPPING_MOVABLE), + page); + page->mapping = (void *)((unsigned long)page->mapping & + PAGE_MAPPING_MOVABLE); +} + /* * migrate_prep() needs to be called before we start compiling a list of pages * to be migrated using isolate_lru_page(). If scheduling work on other CPUs is @@ -73,6 +105,79 @@ int migrate_prep_local(void) return 0; } +bool isolate_movable_page(struct page *page, isolate_mode_t mode) +{ + struct address_space *mapping; + + /* + * Avoid burning cycles with pages that are yet under __free_pages(), + * or just...

...lient_db, mn); + + pr_debug("%s: mm %016lx\n", __func__, (unsigned long)mm); + + /* at this point other threads may already have hold of this cdb */ + client_db_put(cdb); +} + +static void mm_remote_page_unevictable(struct page *page) +{ + VM_BUG_ON_PAGE(!PageLocked(page), page); + + if (!isolate_lru_page(page)) + putback_lru_page(page); +} + +static void mm_remote_page_evictable(struct page *page) +{ + VM_BUG_ON_PAGE(!PageLocked(page), page); + + if (!isolate_lru_page(page)) + putback_lru_page(page); + else { + if (PageUnevictable(page)) + count_vm_event(UNEVICTABLE_PGSTRANDED); + } +} + +void...

...page)); + BUG_ON(PageDirty(page)); + BUG_ON(PagePrivate(page)); + + /* Set the discarded bit early. */ + if (TestSetPageDiscarded(page)) + return; + + /* Unmap the page from all page tables. */ + page_unmap_all(page); + + /* + * Remove the page from LRU if it is currently added. + * The users of isolate_lru_pages need to check the + * discarded bit before readding the page to the LRU. + */ + zone = page_zone(page); + spin_lock_irq(&zone->lru_lock); + if (PageLRU(page)) { + /* Unlink page from lru. */ + __ClearPageLRU(page); + del_page_from_lru(zone, page); + } + spin_unlock_irq(&zone->lr...

...page)); + BUG_ON(PageDirty(page)); + BUG_ON(PagePrivate(page)); + + /* Set the discarded bit early. */ + if (TestSetPageDiscarded(page)) + return; + + /* Unmap the page from all page tables. */ + page_unmap_all(page); + + /* + * Remove the page from LRU if it is currently added. + * The users of isolate_lru_pages need to check the + * discarded bit before readding the page to the LRU. + */ + zone = page_zone(page); + spin_lock_irq(&zone->lru_lock); + if (PageLRU(page)) { + /* Unlink page from lru. */ + __ClearPageLRU(page); + del_page_from_lru(zone, page); + } + spin_unlock_irq(&zone->lr...

Hi All, I''m getting the attached panic in the hypervisor on a Sun 6270 running xen-testing.hg changeset 19913:6063c16aeeaa. I can run xen-3.3.1 from the standard SLES 11 distribution (which says that it''s changeset 18546 but it has many patches). Any ideas? thanks, dan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be migrated with current compaction algorithm which supports only LRU pages. In the end, compaction cannot