From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 508BFA00C5; Mon, 31 Oct 2022 14:38:26 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E9D6C40223; Mon, 31 Oct 2022 14:38:25 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 6E97540151 for ; Mon, 31 Oct 2022 14:38:24 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id EFBC55C013B; Mon, 31 Oct 2022 09:38:21 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 31 Oct 2022 09:38:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1667223501; x= 1667309901; bh=KTyvsOvEcKMrf7V90+KPOVa3EoQpQuSpyXJx8c4THmU=; b=l SpEtSIdFOVpLSiabRkC2321bpLqs0jXRl0AVEtJZAVxIV94mP/YJz9Dt/aCCM8yo 78Vu9O0Ji5ABhTkhABt7gSX6j0j8yRngsOYAEyGQYaejycH2BaUkPdITelM2FqCH mDPj9seJ9KqoRjojS51TUFukDPjxDmhcPn+GDxQhHqfFFSkIkgKnl2fVJj920pEa Cc81Qld0dw05mOb9IJXZ9jqqp4vQHczEk1Eaoup1kbibNeQwK4xPHPl4u5+OZNpH lm1IBW0GxKthfV870Yn0rPTUGQV1DGq1KLE/TiDlfL8guG1oH8NnOnoOcmgcNV9e HQKw+98pd3I1kFsb2VTzg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1667223501; x= 1667309901; bh=KTyvsOvEcKMrf7V90+KPOVa3EoQpQuSpyXJx8c4THmU=; b=N 5pRi/ccIy1r1jTngy02HjGASzAwOuFeWM6aG1O94TfW+QU3Yy68aUFtSgS+znY1C Gjs5Ijisasu9+JBTqen3nIHXOPqON166Zgr0ZLIsN2A1/vI4/RuVZFkQCigvHJ2i UhsW72WhhKnboQgh52HdQ/7YWsdm8ZGcWAS+d1UYBK87LhR3bMooY/YXwfkRD8L8 ekTGfWSmsybeW6/ixbvk7mS87kg5G+41u/d/UOXWMMffTQ/vCxqTD4G3OQsrt9wD RBodHqiLJEH/H+AwTdb8oL/0qJqLe9HEOVbw7T/h/7loQ8OYfEZmS0ILG0Gig+/3 VdRAPblQB2XE6wlA5QCMQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrudefgdehgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvvefufffkjghfggfgtgesthhqre dttddtudenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpedtiedvkefggfeitdegte fggffhgefffefffeejfedtvdejfeehkeegffetvdffteenucffohhmrghinhepihhnthgv lhdrtghomhdpohiilhgrsghsrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 31 Oct 2022 09:38:20 -0400 (EDT) From: Thomas Monjalon To: jingjing.wu@intel.com, beilei.xing@intel.com Cc: dev@dpdk.org, qi.z.zhang@intel.com, helin.zhang@intel.com, andrew.rybchenko@oktetlabs.ru Subject: Re: [PATCH v18 00/18] add support for idpf PMD in DPDK Date: Mon, 31 Oct 2022 14:38:17 +0100 Message-ID: <2618728.KRxA6XjA2N@thomas> In-Reply-To: <20221031083346.16558-1-beilei.xing@intel.com> References: <20221031051556.98549-1-beilei.xing@intel.com> <20221031083346.16558-1-beilei.xing@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 31/10/2022 09:33, beilei.xing@intel.com: > From: Beilei Xing >=20 > This patchset introduced the idpf (Infrastructure Data Path Function) PMD= in DPDK for Intel=AE IPU E2000 (Device ID: 0x1452). > The Intel=AE IPU E2000 targets to deliver high performance under real wor= kloads with security and isolation. > Please refer to > https://www.intel.com/content/www/us/en/products/network-io/infrastructur= e-processing-units/asic/e2000-asic.html > for more information. >=20 > Linux upstream is still ongoing, previous work refers to https://patchwor= k.ozlabs.org/project/intel-wired-lan/patch/20220128001009.721392-20-alan.br= ady@intel.com/. I've fixed/improved doc and build files. Applied, thanks.