From: "Jianjian Huo" <j.huo@alibaba-inc.com>
To: <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK memory error check and offline bad pages
Date: Mon, 13 Nov 2017 13:52:54 +0800 [thread overview]
Message-ID: <2A950137-2E48-41B5-AFD3-5E38E4AAD7D5@alibaba-inc.com> (raw)
In-Reply-To: <8585190C-A984-4563-BF89-97CEFE6B87AB@alibaba-inc.com>
Anyone has any idea on this?
Can’t believe DPDK doesn’t support such an important feature. This is going to be a show stopper for real production system.
-Jianjian
On 11/7/17, 1:13 PM, "Jianjian Huo" <j.huo@alibaba-inc.com> wrote:
Hi dpdk developers,
I have a question regarding how DPDK memory module treats memory errors.
In Linux kernel, it has mechanism (mcelog and EDAC) to monitor the memory controller and report correctable/uncorrectable memory errors. Using some configurations, if memory errors exceed threshold, system can offline bad memory pages and avoid applications to access/crash.
Do we have similar mechanism in DPDK?
Thanks,
Jianjian
next prev parent reply other threads:[~2017-11-13 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 21:13 Jianjian Huo
2017-11-13 5:52 ` Jianjian Huo [this message]
2017-11-13 7:08 ` Tan, Jianfeng
2017-11-13 21:40 ` Wiles, Keith
2017-11-14 0:03 ` Tan, Jianfeng
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=2A950137-2E48-41B5-AFD3-5E38E4AAD7D5@alibaba-inc.com \
--to=j.huo@alibaba-inc.com \
--cc=dev@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).