From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 13191A04C7; Mon, 14 Sep 2020 22:49:57 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E04CEFFA; Mon, 14 Sep 2020 22:49:56 +0200 (CEST) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 06D25E07 for ; Mon, 14 Sep 2020 22:49:54 +0200 (CEST) IronPort-SDR: aogXPO1xPSXmZwDpEmP6x+9tc0+f7lmt904JD/ukIT8xezpd49e9GFpVOpgWk5TEJkKXqX+U1o DJ9o3T0qKYUQ== X-IronPort-AV: E=McAfee;i="6000,8403,9744"; a="146849626" X-IronPort-AV: E=Sophos;i="5.76,427,1592895600"; d="scan'208";a="146849626" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2020 13:49:53 -0700 IronPort-SDR: dQLpnCqmsMsxoNjeFp991a3Ns67ecY0RRCuDnoNTGcKJOxnj3DJotoWdAmr0QnJnhTGlfI+1Uu YjK+76e3PhLQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.76,427,1592895600"; d="scan'208";a="451029404" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga004.jf.intel.com with ESMTP; 14 Sep 2020 13:49:52 -0700 Received: from sivswdev09.ir.intel.com (sivswdev09.ir.intel.com [10.237.217.48]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id 08EKnpw4024091; Mon, 14 Sep 2020 21:49:51 +0100 Received: from sivswdev09.ir.intel.com (localhost [127.0.0.1]) by sivswdev09.ir.intel.com with ESMTP id 08EKnp7F004704; Mon, 14 Sep 2020 21:49:51 +0100 Received: (from lma25@localhost) by sivswdev09.ir.intel.com with LOCAL id 08EKnpQJ004700; Mon, 14 Sep 2020 21:49:51 +0100 Date: Mon, 14 Sep 2020 21:49:51 +0100 From: "Liang, Ma" To: Stephen Hemminger Cc: dev@dpdk.org, david.hunt@intel.com, anatoly.burakov@intel.com Message-ID: <20200914204951.GC13240@sivswdev09.ir.intel.com> References: <1597141666-20621-1-git-send-email-liang.j.ma@intel.com> <1599214740-3927-1-git-send-email-liang.j.ma@intel.com> <20200904093757.1d3e67f3@hermes.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200904093757.1d3e67f3@hermes.lan> Subject: Re: [dpdk-dev] [PATCH v3 1/6] eal: add power management intrinsics 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Stephen, v4 patch will include the l3fwd-power udpate. Regards Liang On 04 Sep 09:37, Stephen Hemminger wrote: > On Fri, 4 Sep 2020 11:18:55 +0100 > Liang Ma wrote: > > > Add two new power management intrinsics, and provide an implementation > > in eal/x86 based on UMONITOR/UMWAIT instructions. The instructions > > are implemented as raw byte opcodes because there is not yet widespread > > compiler support for these instructions. > > > > The power management instructions provide an architecture-specific > > function to either wait until a specified TSC timestamp is reached, or > > optionally wait until either a TSC timestamp is reached or a memory > > location is written to. The monitor function also provides an optional > > comparison, to avoid sleeping when the expected write has already > > happened, and no more writes are expected. > > > > Signed-off-by: Liang Ma > > Signed-off-by: Anatoly Burakov > > This looks like a useful feature but needs more documentation and example. > It would make sense to put an example in l3fwd-power. >