From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mhocko@suse.com" <mhocko@suse.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"minchan@kernel.org" <minchan@kernel.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"guohanjun@huawei.com" <guohanjun@huawei.com>,
"qiuxishi@huawei.com" <qiuxishi@huawei.com>
Subject: Re: [RFC] HWPOISON: soft offlining for non-lru movable page
Date: Mon, 23 Jan 2017 04:26:40 +0000 [thread overview]
Message-ID: <20170123042639.GA5610@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <ccf71cb7-3a12-0bf4-ad79-b235f6df94c6@huawei.com>
On Fri, Jan 20, 2017 at 05:52:13PM +0800, Yisheng Xie wrote:
> Hi Naoya,
>
> On 2017/1/18 17:45, Naoya Horiguchi wrote:
> > On Wed, Jan 18, 2017 at 12:00:54PM +0800, Yisheng Xie wrote:
> >> This patch is to extends soft offlining framework to support
> >> non-lru page, which already support migration after
> >> commit bda807d44454 ("mm: migrate: support non-lru movable page
> >> migration")
> >>
> >> When memory corrected errors occur on a non-lru movable page,
> >> we can choose to stop using it by migrating data onto another
> >> page and disable the original (maybe half-broken) one.
> >>
> >> Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
> >
> > It looks OK in my quick glance. I'll do some testing more tomorrow.
> >
> Thanks for reviewing.
> I have do some basic test like offline movable page and unpoison it.
> Do you have some test suit or test suggestion? So I can do some more
> test of it for double check? Very thanks for that.
I've tried soft offline on zram pages with your v2 patch, and it works fine.
I have no specific suggestion about other testcases.
Thanks,
Naoya Horiguchi
--
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 prev parent reply other threads:[~2017-01-23 4:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 4:00 Yisheng Xie
2017-01-18 9:45 ` Naoya Horiguchi
2017-01-20 9:52 ` Yisheng Xie
2017-01-23 4:26 ` Naoya Horiguchi [this message]
2017-01-18 9:51 ` Michal Hocko
2017-01-19 1:21 ` Yisheng Xie
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=20170123042639.GA5610@hori1.linux.bs1.fc.nec.co.jp \
--to=n-horiguchi@ah.jp.nec.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=qiuxishi@huawei.com \
--cc=vbabka@suse.cz \
--cc=xieyisheng1@huawei.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox