From: ysxie@foxmail.com To: linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: n-horiguchi@ah.jp.nec.com, mhocko@suse.com, akpm@linux-foundation.org, minchan@kernel.org, vbabka@suse.cz, guohanjun@huawei.com, qiuxishi@huawei.com Subject: [PATCH v4 0/2] HWPOISON: soft offlining for non-lru movable page Date: Wed, 25 Jan 2017 23:05:36 +0800 [thread overview] Message-ID: <1485356738-4831-1-git-send-email-ysxie@foxmail.com> (raw) From: Yisheng Xie <xieyisheng1@huawei.com> Hi Andrew, Could you please help to abandon the v3 of this patch for it will compile error with CONFIG_MIGRATION=n, and it also has error path handling problem. Hi Michal, Minchan and all, Could you please help to review it? Any suggestion is more than welcome. The aim of this patchset is to support soft offlining of movable no-lru pages, which already support migration after Minchan's commit bda807d44454 ("mm: migrate: support non-lru movable page migration"). That means this patch heavily depend on non-lru movable page migration. So when memory corrected errors occur on a non-lru movable page, we can stop to use it by migrating data onto another page and disable the original (maybe half-broken) one. -------- v4: * make isolate_movable_page always defined to avoid compile error with CONFIG_MIGRATION = n * return -EBUSY when isolate_movable_page return false which means failed to isolate movable page. v3: * delete some unneed limitation and use !__PageMovable instead of PageLRU after isolate page to avoid isolated count mismatch, as Minchan Kim's suggestion. v2: * delete function soft_offline_movable_page() and hanle non-lru movable page in __soft_offline_page() as Michal Hocko suggested. Yisheng Xie (2): mm/migration: make isolate_movable_page always defined HWPOISON: soft offlining for non-lru movable page include/linux/migrate.h | 2 ++ mm/memory-failure.c | 26 ++++++++++++++++---------- 2 files changed, 18 insertions(+), 10 deletions(-) -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: ysxie@foxmail.com To: linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: n-horiguchi@ah.jp.nec.com, mhocko@suse.com, akpm@linux-foundation.org, minchan@kernel.org, vbabka@suse.cz, guohanjun@huawei.com, qiuxishi@huawei.com Subject: [PATCH v4 0/2] HWPOISON: soft offlining for non-lru movable page Date: Wed, 25 Jan 2017 23:05:36 +0800 [thread overview] Message-ID: <1485356738-4831-1-git-send-email-ysxie@foxmail.com> (raw) From: Yisheng Xie <xieyisheng1@huawei.com> Hi Andrew, Could you please help to abandon the v3 of this patch for it will compile error with CONFIG_MIGRATION=n, and it also has error path handling problem. Hi Michal, Minchan and all, Could you please help to review it? Any suggestion is more than welcome. The aim of this patchset is to support soft offlining of movable no-lru pages, which already support migration after Minchan's commit bda807d44454 ("mm: migrate: support non-lru movable page migration"). That means this patch heavily depend on non-lru movable page migration. So when memory corrected errors occur on a non-lru movable page, we can stop to use it by migrating data onto another page and disable the original (maybe half-broken) one. -------- v4: * make isolate_movable_page always defined to avoid compile error with CONFIG_MIGRATION = n * return -EBUSY when isolate_movable_page return false which means failed to isolate movable page. v3: * delete some unneed limitation and use !__PageMovable instead of PageLRU after isolate page to avoid isolated count mismatch, as Minchan Kim's suggestion. v2: * delete function soft_offline_movable_page() and hanle non-lru movable page in __soft_offline_page() as Michal Hocko suggested. Yisheng Xie (2): mm/migration: make isolate_movable_page always defined HWPOISON: soft offlining for non-lru movable page include/linux/migrate.h | 2 ++ mm/memory-failure.c | 26 ++++++++++++++++---------- 2 files changed, 18 insertions(+), 10 deletions(-) -- 1.9.1 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-01-25 15:05 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-01-25 15:05 ysxie [this message] 2017-01-25 15:05 ` [PATCH v4 0/2] HWPOISON: soft offlining for non-lru movable page ysxie 2017-01-25 15:05 ` [PATCH v4 1/2] mm/migration: make isolate_movable_page always defined ysxie 2017-01-25 15:05 ` ysxie 2017-01-26 9:18 ` Michal Hocko 2017-01-26 9:18 ` Michal Hocko 2017-01-30 14:59 ` Yisheng Xie 2017-01-30 14:59 ` Yisheng Xie 2017-01-30 15:13 ` Michal Hocko 2017-01-30 15:13 ` Michal Hocko 2017-01-25 15:05 ` [PATCH v4 2/2] HWPOISON: soft offlining for non-lru movable page ysxie 2017-01-25 15:05 ` ysxie 2017-01-26 9:27 ` Michal Hocko 2017-01-26 9:27 ` Michal Hocko 2017-01-30 15:04 ` Yisheng Xie 2017-01-30 15:04 ` Yisheng Xie 2017-01-30 16:38 ` Michal Hocko 2017-01-30 16:38 ` Michal Hocko
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1485356738-4831-1-git-send-email-ysxie@foxmail.com \ --to=ysxie@foxmail.com \ --cc=akpm@linux-foundation.org \ --cc=guohanjun@huawei.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@suse.com \ --cc=minchan@kernel.org \ --cc=n-horiguchi@ah.jp.nec.com \ --cc=qiuxishi@huawei.com \ --cc=vbabka@suse.cz \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.