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 D343AA04B5; Wed, 16 Sep 2020 18:34:28 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3FEE21C437; Wed, 16 Sep 2020 18:34:28 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 326BB1C436 for ; Wed, 16 Sep 2020 18:34:26 +0200 (CEST) IronPort-SDR: sBcVfyqYaFDoE4qySkurjONCdw41eldc2KU/PH5hCEEmC7F131zjzEw1mKjwun0KbHhU8JwhJk 893WqiIpWKCg== X-IronPort-AV: E=McAfee;i="6000,8403,9746"; a="147264515" X-IronPort-AV: E=Sophos;i="5.76,433,1592895600"; d="scan'208";a="147264515" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Sep 2020 09:34:22 -0700 IronPort-SDR: 3LetiNfkOOxQ82N4nNPCOqoAVmoE2rg8E+J03xy2WPdYjhOna/sZrwQEj0XTTFrz4365gvE4Vs 429/lqQELbeg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.76,433,1592895600"; d="scan'208";a="307105118" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga006.jf.intel.com with ESMTP; 16 Sep 2020 09:34:21 -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 08GGYK20030416; Wed, 16 Sep 2020 17:34:20 +0100 Received: from sivswdev09.ir.intel.com (localhost [127.0.0.1]) by sivswdev09.ir.intel.com with ESMTP id 08GGYKQw005799; Wed, 16 Sep 2020 17:34:20 +0100 Received: (from lma25@localhost) by sivswdev09.ir.intel.com with LOCAL id 08GGYJ3C005795; Wed, 16 Sep 2020 17:34:19 +0100 Date: Wed, 16 Sep 2020 17:34:19 +0100 From: "Liang, Ma" To: Stephen Hemminger Cc: dev@dpdk.org, david.hunt@intel.com, anatoly.burakov@intel.com Message-ID: <20200916163419.GA1849@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 have discussed with arm developer in the past. Please ref https://patches.dpdk.org/patch/70662/ There was no objection, in my opinoin. Also the API we proposed has experimental tag, other vendor still can change it. For the ethdev internal ops we introduced should work with any NIC use ring descriptor writeback mechansim. But we lack the internal sight of Mellanox or Broadcom NIC. AF_XDP PMD and virtio-net is under investigation. I hope above explaination addressed your concern. > 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. > > Will it work in a VM? Will it work with virtio or vmxnet3? > > 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.