From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 004EB1B34A for ; Mon, 13 Nov 2017 22:40:15 +0100 (CET) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Nov 2017 13:40:14 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,389,1505804400"; d="scan'208";a="173110626" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga005.jf.intel.com with ESMTP; 13 Nov 2017 13:40:14 -0800 Received: from fmsmsx151.amr.corp.intel.com (10.18.125.4) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 13 Nov 2017 13:40:14 -0800 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.51]) by FMSMSX151.amr.corp.intel.com ([169.254.7.181]) with mapi id 14.03.0319.002; Mon, 13 Nov 2017 13:40:08 -0800 From: "Wiles, Keith" To: "Tan, Jianfeng" CC: Jianjian Huo , "dev@dpdk.org" Thread-Topic: [dpdk-dev] DPDK memory error check and offline bad pages Thread-Index: AQHTWA1EDqqoCX+XYEKS2OUCrCyvI6MScmKAgADzkYA= Date: Mon, 13 Nov 2017 21:40:07 +0000 Message-ID: <4F0B926E-5BC4-43C4-8DD6-FCEF4B811795@intel.com> References: <8585190C-A984-4563-BF89-97CEFE6B87AB@alibaba-inc.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.131.232] Content-Type: text/plain; charset="us-ascii" Content-ID: <467A1397C6C6E3428D76CCEF91829864@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2017 21:40:16 -0000 > On Nov 12, 2017, at 11:08 PM, Tan, Jianfeng wrot= e: >=20 > Hi Jianjian, >=20 >> -----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 >>=20 >> Hi dpdk developers, >>=20 >> I have a question regarding how DPDK memory module treats memory >> errors. >=20 > You mean hardware error which cannot be fixed by ECC? >=20 >>=20 >> In Linux kernel, it has mechanism (mcelog and EDAC) to monitor the memor= y >> controller and report correctable/uncorrectable memory errors. Using som= e >> configurations, if memory errors exceed threshold, system can offline ba= d >> memory pages and avoid applications to access/crash. >=20 > DPDK app is just one of applications. Are there any framework to notify s= uch error to applications? > To notify is the first thing, to recover is another thing which takes mor= e effort. >=20 >> Do we have similar mechanism in DPDK? >=20 > No, as far as I know. Because DPDK runs as a normal user space application in Linux then the curr= ent features in the Linux Kernel can be used correct? >=20 > Thanks, > Jianfeng >=20 >>=20 >> Thanks, >> Jianjian >>=20 >=20 Regards, Keith