From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailfilter01.viettel.com.vn (mailfilter01.viettel.com.vn [125.235.240.53]) by dpdk.org (Postfix) with ESMTP id D8A795F20 for ; Fri, 2 Mar 2018 08:19:12 +0100 (CET) X-IronPort-AV: E=Sophos;i="5.47,411,1515430800"; d="scan'208,217";a="73656895" Received: from 125.235.240.45.adsl.viettel.vn (HELO mta2.viettel.com.vn) ([125.235.240.45]) by mailfilter01.viettel.com.vn with ESMTP; 02 Mar 2018 14:19:06 +0700 Received: from localhost (localhost [127.0.0.1]) by mta2.viettel.com.vn (Postfix) with ESMTP id 4BEB4689F1A; Fri, 2 Mar 2018 14:18:56 +0700 (ICT) Received: from mta2.viettel.com.vn ([127.0.0.1]) by localhost (mta2.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id PVvD3jUeNyik; Fri, 2 Mar 2018 14:18:56 +0700 (ICT) Received: from localhost (localhost [127.0.0.1]) by mta2.viettel.com.vn (Postfix) with ESMTP id 2A8CD689EED; Fri, 2 Mar 2018 14:18:56 +0700 (ICT) X-Virus-Scanned: amavisd-new at Received: from mta2.viettel.com.vn ([127.0.0.1]) by localhost (mta2.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id FfTPwGveu15A; Fri, 2 Mar 2018 14:18:56 +0700 (ICT) Received: from ANMLONGTB5 (unknown [27.68.241.28]) by mta2.viettel.com.vn (Postfix) with ESMTPSA id F3CDD689F1A; Fri, 2 Mar 2018 14:18:55 +0700 (ICT) To: Cc: , , , Message-ID: <000201d3b1f7$4b622cc0$e2268640$@viettel.com.vn> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AdOx9x+6lgNr/UirQjmixSNLWTOiTw== MilterAction: FORWARD Date: Fri, 2 Mar 2018 14:18:56 +0700 (ICT) From: longtb5@viettel.com.vn Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] librte_power w/ intel_pstate cpufreq governor 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: Fri, 02 Mar 2018 07:19:13 -0000 Hi everybody, I know this thread was from over 2 years ago but I ran into the same problem with l3fwd-power today. Any updates on this? -BL