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 EF419A04C7; Mon, 14 Sep 2020 23:12:22 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 187CD1BFC4; Mon, 14 Sep 2020 23:12:22 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 03C401BE98 for ; Mon, 14 Sep 2020 23:12:20 +0200 (CEST) IronPort-SDR: UV90bKLnfnr2ukCIiqKht+xWnQVRx3siyi4Hnrsx9Wgprbyd5+XNovMidMm51klj44Bdhnu9Xr CibVtiNTunGQ== X-IronPort-AV: E=McAfee;i="6000,8403,9744"; a="146901994" X-IronPort-AV: E=Sophos;i="5.76,427,1592895600"; d="scan'208";a="146901994" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2020 14:12:19 -0700 IronPort-SDR: ogwl7PKS/cnZr6Xognc6oElgSyxRlk//DyzRm8d86MEkwaOceodKvS4TUxcD39NSG6L6iSIft/ EfcpWGcItxOQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.76,427,1592895600"; d="scan'208";a="287750502" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by fmsmga008.fm.intel.com with ESMTP; 14 Sep 2020 14:12:18 -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 08ELCIVU000762; Mon, 14 Sep 2020 22:12:18 +0100 Received: from sivswdev09.ir.intel.com (localhost [127.0.0.1]) by sivswdev09.ir.intel.com with ESMTP id 08ELCHwh000435; Mon, 14 Sep 2020 22:12:17 +0100 Received: (from lma25@localhost) by sivswdev09.ir.intel.com with LOCAL id 08ELCH2T000431; Mon, 14 Sep 2020 22:12:17 +0100 Date: Mon, 14 Sep 2020 22:12:17 +0100 From: "Liang, Ma" To: Stephen Hemminger Cc: dev@dpdk.org, david.hunt@intel.com, anatoly.burakov@intel.com Message-ID: <20200914211217.GB27127@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> <20200904114237.1586821a@hermes.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200904114237.1586821a@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" On 04 Sep 11:42, Stephen Hemminger wrote: we are very open to discuss design with other vendor. > Before this is merged, please work with Arm maintainers to have a version that > works on Arm 64 as well. Don't think this should be merged unless the two major > platforms supported by DPDK can work with it. > Also, not sure if this mechanism can work with other drivers. You need to > work with other vendors to show that the same infrastructure can work with > their hardware. Once again, I don't think this can go in if it only can > work on Intel. It needs to work on Broadcom, Mellanox to be useful. this mechanism should work with any device use a HW ring descriptor mechanism. I think most Mellanox and Broadcom NIC can support it easily. > Will it work in a VM? Will it work with virtio or vmxnet3? > General speaking, Guest OS is not very easy to use this. However, virtio is under invetigation. > Having a single vendor solution is a non-starter for me. > They don't all have to be there to get it merged, but if the design only > works on single platform then it is not helpful.