[dpdk-dev] DPDK memory error check and offline bad pages

Tan, Jianfeng jianfeng.tan at intel.com
Tue Nov 14 01:03:59 CET 2017



On 11/14/2017 5:40 AM, Wiles, Keith wrote:
>
>> On Nov 12, 2017, at 11:08 PM, Tan, Jianfeng <jianfeng.tan at intel.com> wrote:
>>
>> Hi Jianjian,
>>
>>> -----Original Message-----
>>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jianjian Huo
>>> Sent: Wednesday, November 8, 2017 5:13 AM
>>> To: dev at 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?

I suppose so, but we still have not leveraged any of those features 
explicitly AFAIK. Implicitly? Tend to be problematic, as DPDK only 
translates physical address once at the very beginning.

Thanks,
Jianfeng

>
>> Thanks,
>> Jianfeng
>>
>>> Thanks,
>>> Jianjian
>>>
> Regards,
> Keith
>



More information about the dev mailing list