From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <j.huo@alibaba-inc.com>
Received: from out0-211.mail.aliyun.com (out0-211.mail.aliyun.com
 [140.205.0.211]) by dpdk.org (Postfix) with ESMTP id 5D41B1B2FD
 for <dev@dpdk.org>; Tue,  7 Nov 2017 22:13:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=alibaba-inc.com; s=default;
 t=1510089185; h=Date:Subject:From:To:Message-ID:Mime-version:Content-type;
 bh=SBu9yLvsJkU2XeXqh53wU6wBj58xUEPW9m9wfA5fLYQ=;
 b=GOylr0/JnfptcXP812TprifjL5ioSnA06brtb4r5oiNG264Jt6h4ozokbFpwyDRka5gTI9F/3VXbYkKBAeNJ8/wgTSbcn1yMvzWVs21znhMeEYyzgXvQzlGNu82dyqcw0LcpF0Eu7TquW7tNwPUysRMNNw5ndtZ4ruHBO6eFlXM=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R101e4;
 FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03295; MF=j.huo@alibaba-inc.com; NM=1; PH=DS;
 RN=1; SR=0; TI=SMTPD_---.9LoqEyK_1510089183; 
Received: from 192.168.0.199(mailfrom:j.huo@alibaba-inc.com ip:121.0.29.201)
 by smtp.aliyun-inc.com(127.0.0.1); Wed, 08 Nov 2017 05:13:04 +0800
User-Agent: Microsoft-MacOutlook/f.23.0.170610
Date: Wed, 08 Nov 2017 05:13:01 +0800
From: "Jianjian Huo" <j.huo@alibaba-inc.com>
To: <dev@dpdk.org>
Message-ID: <8585190C-A984-4563-BF89-97CEFE6B87AB@alibaba-inc.com>
Thread-Topic: DPDK memory error check and offline bad pages
Mime-version: 1.0
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: 7bit
Subject: [dpdk-dev] DPDK memory error check and offline bad pages
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Nov 2017 21:13:10 -0000

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