From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>
Cc: Jianjian Huo <j.huo@alibaba-inc.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK memory error check and offline bad pages
Date: Mon, 13 Nov 2017 21:40:07 +0000 [thread overview]
Message-ID: <4F0B926E-5BC4-43C4-8DD6-FCEF4B811795@intel.com> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E365134DD1E@SHSMSX103.ccr.corp.intel.com>
> On Nov 12, 2017, at 11:08 PM, Tan, Jianfeng <jianfeng.tan@intel.com> wrote:
>
> Hi Jianjian,
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jianjian Huo
>> Sent: Wednesday, November 8, 2017 5:13 AM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] DPDK memory error check and offline bad pages
>>
>> Hi dpdk developers,
>>
>> I have a question regarding how DPDK memory module treats memory
>> errors.
>
> You mean hardware error which cannot be fixed by ECC?
>
>>
>> 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.
>
> DPDK app is just one of applications. Are there any framework to notify such error to applications?
> To notify is the first thing, to recover is another thing which takes more effort.
>
>> Do we have similar mechanism in DPDK?
>
> No, as far as I know.
Because DPDK runs as a normal user space application in Linux then the current features in the Linux Kernel can be used correct?
>
> Thanks,
> Jianfeng
>
>>
>> Thanks,
>> Jianjian
>>
>
Regards,
Keith
next prev parent reply other threads:[~2017-11-13 21:40 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
2017-11-13 7:08 ` Tan, Jianfeng
2017-11-13 21:40 ` Wiles, Keith [this message]
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=4F0B926E-5BC4-43C4-8DD6-FCEF4B811795@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=j.huo@alibaba-inc.com \
--cc=jianfeng.tan@intel.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;
as well as URLs for NNTP newsgroup(s).