From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailfilter03.viettel.com.vn (mailfilter03.viettel.com.vn [125.235.240.55]) by dpdk.org (Postfix) with ESMTP id 76534231E for ; Thu, 29 Mar 2018 16:35:00 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.48,376,1517850000"; d="scan'208";a="74979226" Received: from 125.235.240.44.adsl.viettel.vn (HELO mta1.viettel.com.vn) ([125.235.240.44]) by mailfilter03.viettel.com.vn with ESMTP; 29 Mar 2018 21:34:58 +0700 Received: from localhost (localhost [127.0.0.1]) by mta1.viettel.com.vn (Postfix) with ESMTP id 7544C61CB3D; Thu, 29 Mar 2018 21:34:55 +0700 (ICT) Received: from mta1.viettel.com.vn ([127.0.0.1]) by localhost (mta1.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id uYi9-rdr5n0S; Thu, 29 Mar 2018 21:34:55 +0700 (ICT) Received: from localhost (localhost [127.0.0.1]) by mta1.viettel.com.vn (Postfix) with ESMTP id 5184A61CB3E; Thu, 29 Mar 2018 21:34:55 +0700 (ICT) X-Virus-Scanned: amavisd-new at Received: from mta1.viettel.com.vn ([127.0.0.1]) by localhost (mta1.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BBK_RlLdIlck; Thu, 29 Mar 2018 21:34:55 +0700 (ICT) Received: from mailbox.viettel.com.vn (mailbox7.viettel.com.vn [10.30.182.164]) by mta1.viettel.com.vn (Postfix) with ESMTP id 142AF61CB3D; Thu, 29 Mar 2018 21:34:55 +0700 (ICT) To: wei dai Cc: Keith Wiles , Vincent Jardin , users@dpdk.org, toanln1 Message-ID: <951240770.3346891.1522334094790.JavaMail.zimbra@viettel.com.vn> In-Reply-To: <49759EB36A64CF4892C1AFEC9231E8D66CF63AAA@PGSMSX112.gar.corp.intel.com> References: <287310953.2822437.1522234072488.JavaMail.zimbra@viettel.com.vn> <1626c4b73f8.27fc.bb328046f2889bc8f44aafa891a44dd2@6wind.com> <3E2BA059-6902-4827-816F-9DD50BEF370F@intel.com> <49759EB36A64CF4892C1AFEC9231E8D66CF63AAA@PGSMSX112.gar.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [203.113.138.20] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - GC64 (Linux)/8.0.9_GA_6191) Thread-Topic: [dpdk-users] Temperature of CPU when running DPDK App Thread-Index: AdPGl2hYYqVp48MOS26B2qEuePmZ44PfeKKk MilterAction: FORWARD Date: Thu, 29 Mar 2018 21:34:55 +0700 (ICT) From: vuonglv@viettel.com.vn Subject: Re: [dpdk-users] Temperature of CPU when running DPDK App X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2018 14:35:02 -0000 Hi team, Thanks for your response, but my question related to safe temperature threshold for CPU. I mean, if temperature of CPU is higher than recommended in long time, it may be reduce service life of CPU. Do you have any knowledge or reference related to this problem? Many thanks, Vuong Le ----- Original Message ----- From: "wei dai" To: "Keith Wiles" , "Vincent Jardin" Cc: vuonglv@viettel.com.vn, users@dpdk.org, "toanln1" Sent: Wednesday, March 28, 2018 8:19:35 PM Subject: RE: [dpdk-users] Temperature of CPU when running DPDK App Example/l3fwd-power can be a good reference. > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Wiles, Keith > Sent: Wednesday, March 28, 2018 8:24 PM > To: Vincent Jardin > Cc: vuonglv@viettel.com.vn; users@dpdk.org; toanln1 > > Subject: Re: [dpdk-users] Temperature of CPU when running DPDK App > > > > > On Mar 28, 2018, at 6:08 AM, Vincent Jardin > wrote: > > > > Did you try interrupt mode ? > > > > Also look at rte_pause() while you detect nothing to do before going back to > interrupt mode can help too. > > > > Regards, > Keith