Message ID | 20220905105828.3190335-1-junfeng.guo@intel.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3384BA054F; Mon, 5 Sep 2022 12:58:37 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DD38740695; Mon, 5 Sep 2022 12:58:36 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id DC26D400D6 for <dev@dpdk.org>; Mon, 5 Sep 2022 12:58:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1662375516; x=1693911516; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=T4xiJ0mZj1i/+3Sibpl49ZFmLmo9oqbc1Xt6kfkCBXI=; b=jn4sIHDkgydjsOBlJerlGTC0fN/1DCQuNoV/eLZB9CSgqQcbrMj2409P PS/gcdTqKP2JAX8KARC4ZEyHyzPrLD4aQ+gMidiVrhGzVPz02pJTlB4FS MQ/OZ9/cAIV/9unwYgK21UPvj5C7x4ZLJ3MvbmwYYs5v8TOvP/uTV/mMn z0ymmlz5qlEqiGS19iZY0TqO9/1QbpBj6sHIa14Z2I9XHtSfdh18+VM3q 6PAuQxJBsFuhKnPaLKCcdlvVqkjCLr+DMAKmgHM53Ptw+cuZHrJ3JH879 Tkoo4vYR5wlMxXjd2lodcgRQoz9QMxTwz9PM22GSSakJwRrN8M4ZUAAGX A==; X-IronPort-AV: E=McAfee;i="6500,9779,10460"; a="297676280" X-IronPort-AV: E=Sophos;i="5.93,291,1654585200"; d="scan'208";a="297676280" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Sep 2022 03:58:34 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.93,291,1654585200"; d="scan'208";a="682023823" Received: from dpdk-jf-ntb-v2.sh.intel.com ([10.67.118.246]) by fmsmga004.fm.intel.com with ESMTP; 05 Sep 2022 03:58:31 -0700 From: Junfeng Guo <junfeng.guo@intel.com> To: qi.z.zhang@intel.com, jingjing.wu@intel.com, beilei.xing@intel.com Cc: dev@dpdk.org, xiao.w.wang@intel.com, junfeng.guo@intel.com Subject: [PATCH v2 00/14] add support for idpf PMD in DPDK Date: Mon, 5 Sep 2022 18:58:14 +0800 Message-Id: <20220905105828.3190335-1-junfeng.guo@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20220803113104.1184059-1-junfeng.guo@intel.com> References: <20220803113104.1184059-1-junfeng.guo@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org |
Series |
add support for idpf PMD in DPDK
|
|
Message
Junfeng Guo
Sept. 5, 2022, 10:58 a.m. UTC
This patchset introduced the idpf (Infrastructure Data Path Function) PMD [*EXPERIMENTAL*] in DPDK for Intel Device ID of 0x1452. v2: fixed some coding style issues and did some refactors. Junfeng Guo (14): net/idpf/base: introduce base code net/idpf/base: add logs and OS specific implementation net/idpf: add support for device initialization net/idpf: add support for queue operations net/idpf: add support for device information get net/idpf: add support for packet type get net/idpf: add support for link status update net/idpf: add support for basic Rx/Tx datapath net/idpf: add support for RSS net/idpf: add support for mtu configuration net/idpf: add support for hw statistics net/idpf: add support for write back based on ITR expire net/idpf: add AVX512 data path for single queue model net/idpf: add support for timestamp offload drivers/net/idpf/base/iecm_alloc.h | 22 + drivers/net/idpf/base/iecm_common.c | 359 +++ drivers/net/idpf/base/iecm_controlq.c | 662 ++++ drivers/net/idpf/base/iecm_controlq.h | 214 ++ drivers/net/idpf/base/iecm_controlq_api.h | 227 ++ drivers/net/idpf/base/iecm_controlq_setup.c | 179 ++ drivers/net/idpf/base/iecm_devids.h | 18 + drivers/net/idpf/base/iecm_lan_pf_regs.h | 134 + drivers/net/idpf/base/iecm_lan_txrx.h | 428 +++ drivers/net/idpf/base/iecm_lan_vf_regs.h | 114 + drivers/net/idpf/base/iecm_osdep.h | 365 +++ drivers/net/idpf/base/iecm_prototype.h | 45 + drivers/net/idpf/base/iecm_type.h | 106 + drivers/net/idpf/base/meson.build | 27 + drivers/net/idpf/base/siov_regs.h | 41 + drivers/net/idpf/base/virtchnl.h | 2743 +++++++++++++++++ drivers/net/idpf/base/virtchnl2.h | 1411 +++++++++ drivers/net/idpf/base/virtchnl2_lan_desc.h | 603 ++++ drivers/net/idpf/base/virtchnl_inline_ipsec.h | 567 ++++ drivers/net/idpf/idpf_ethdev.c | 1341 ++++++++ drivers/net/idpf/idpf_ethdev.h | 270 ++ drivers/net/idpf/idpf_logs.h | 38 + drivers/net/idpf/idpf_rxtx.c | 2393 ++++++++++++++ drivers/net/idpf/idpf_rxtx.h | 322 ++ drivers/net/idpf/idpf_rxtx_vec_avx512.c | 917 ++++++ drivers/net/idpf/idpf_rxtx_vec_common.h | 89 + drivers/net/idpf/idpf_vchnl.c | 1470 +++++++++ drivers/net/idpf/meson.build | 48 + drivers/net/idpf/version.map | 3 + drivers/net/meson.build | 1 + 30 files changed, 15157 insertions(+) create mode 100644 drivers/net/idpf/base/iecm_alloc.h create mode 100644 drivers/net/idpf/base/iecm_common.c create mode 100644 drivers/net/idpf/base/iecm_controlq.c create mode 100644 drivers/net/idpf/base/iecm_controlq.h create mode 100644 drivers/net/idpf/base/iecm_controlq_api.h create mode 100644 drivers/net/idpf/base/iecm_controlq_setup.c create mode 100644 drivers/net/idpf/base/iecm_devids.h create mode 100644 drivers/net/idpf/base/iecm_lan_pf_regs.h create mode 100644 drivers/net/idpf/base/iecm_lan_txrx.h create mode 100644 drivers/net/idpf/base/iecm_lan_vf_regs.h create mode 100644 drivers/net/idpf/base/iecm_osdep.h create mode 100644 drivers/net/idpf/base/iecm_prototype.h create mode 100644 drivers/net/idpf/base/iecm_type.h create mode 100644 drivers/net/idpf/base/meson.build create mode 100644 drivers/net/idpf/base/siov_regs.h create mode 100644 drivers/net/idpf/base/virtchnl.h create mode 100644 drivers/net/idpf/base/virtchnl2.h create mode 100644 drivers/net/idpf/base/virtchnl2_lan_desc.h create mode 100644 drivers/net/idpf/base/virtchnl_inline_ipsec.h create mode 100644 drivers/net/idpf/idpf_ethdev.c create mode 100644 drivers/net/idpf/idpf_ethdev.h create mode 100644 drivers/net/idpf/idpf_logs.h create mode 100644 drivers/net/idpf/idpf_rxtx.c create mode 100644 drivers/net/idpf/idpf_rxtx.h create mode 100644 drivers/net/idpf/idpf_rxtx_vec_avx512.c create mode 100644 drivers/net/idpf/idpf_rxtx_vec_common.h create mode 100644 drivers/net/idpf/idpf_vchnl.c create mode 100644 drivers/net/idpf/meson.build create mode 100644 drivers/net/idpf/version.map
Comments
On 9/5/22 13:58, Junfeng Guo wrote: > This patchset introduced the idpf (Infrastructure Data Path Function) > PMD [*EXPERIMENTAL*] in DPDK for Intel Device ID of 0x1452. > > v2: > fixed some coding style issues and did some refactors. The patch series should: - add entry in MAINTAINERS - add driver documentation to doc/guides/nics/idpf.rst - advertise the driver in release notes - when features are added it should be added to doc/guides/nics/features/idpf.ini
On 10/3/22 16:31, Andrew Rybchenko wrote: > On 9/5/22 13:58, Junfeng Guo wrote: >> This patchset introduced the idpf (Infrastructure Data Path Function) >> PMD [*EXPERIMENTAL*] in DPDK for Intel Device ID of 0x1452. >> >> v2: >> fixed some coding style issues and did some refactors. > > The patch series should: > - add entry in MAINTAINERS > - add driver documentation to doc/guides/nics/idpf.rst > - advertise the driver in release notes > - when features are added it should be added to > doc/guides/nics/features/idpf.ini I'd really like to add one more point. There is a long road for the driver to be accepted since many changes are required, but it is definitely doable. More important to get replies on generic questions. What is it? What is the HW? Is it released? Where I can read about it?
> -----Original Message----- > From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> > Sent: Monday, October 3, 2022 22:36 > To: Guo, Junfeng <junfeng.guo@intel.com>; Zhang, Qi Z > <qi.z.zhang@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>; Xing, > Beilei <beilei.xing@intel.com> > Cc: dev@dpdk.org; Wang, Xiao W <xiao.w.wang@intel.com> > Subject: Re: [PATCH v2 00/14] add support for idpf PMD in DPDK > > On 10/3/22 16:31, Andrew Rybchenko wrote: > > On 9/5/22 13:58, Junfeng Guo wrote: > >> This patchset introduced the idpf (Infrastructure Data Path Function) > >> PMD [*EXPERIMENTAL*] in DPDK for Intel Device ID of 0x1452. > >> > >> v2: > >> fixed some coding style issues and did some refactors. > > > > The patch series should: > > - add entry in MAINTAINERS > > - add driver documentation to doc/guides/nics/idpf.rst > > - advertise the driver in release notes > > - when features are added it should be added to > > doc/guides/nics/features/idpf.ini Sure, thanks for your advice! We will improve the commit order and items in the coming versions. Currently we are still trying to improve the description related files. Please also help review for the coming versions, thanks a lot! > > I'd really like to add one more point. > There is a long road for the driver to be accepted since > many changes are required, but it is definitely doable. > > More important to get replies on generic questions. > What is it? What is the HW? Is it released? > Where I can read about it? Well, this is the new ``idpf`` net driver for Intel® IPU Ethernet ES2000 Series. The spec has not been released at this point. Could you help review the coming version patch set, thanks!