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 44EA3A0093; Mon, 2 May 2022 12:29:46 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F2C1940F35; Mon, 2 May 2022 12:29:45 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id A7EDD40E28 for ; Mon, 2 May 2022 12:29:44 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 2250F5C00EE; Mon, 2 May 2022 06:29:42 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 02 May 2022 06:29:42 -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=fm1; t=1651487382; x= 1651573782; bh=385GupUKA/ZoWMWFex8TJea5dUg2sq8WsgxLF8W/PZ0=; b=o 4YFKBcAalb03E/mXHn8MnSynWeNB6zvjP+xpG4+lfpkI9wg9zOlkZLO/njQttN7Y Pc7T3rTH/0kuVLl9QSbONOW1Ce4Uong7E72i94aqUqQN/NDqaI18pvACj5iz7ItY a1Zri/4yxNCRGKGkW63bMfdNr3i2HU1pe45LOL3Pvq9zr6vShZHhykuXP75DeLUi 6S4wkKv+hDkx5dWveO0aYf568rq4UA+vx4g+Ui0DkMgwaRh8EAhBMsOAn680DzvT 0sNuc48dCdnvQXNQ5xZtIYtSXZmyEsqUVQsrI6xR2EiXDgDXUFOgy1PsSCqvBwVl QIqvoAIxoQ6mUFJKNSEdQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; 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:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1651487382; x=1651573782; bh=385GupUKA/ZoW MWFex8TJea5dUg2sq8WsgxLF8W/PZ0=; b=o4KMq5E2cbB6cRFkjFjz/96GHGP6a 77CTG8M3B09rDBrFzoLEXLZvui9N/kmPNpb7BIaRwfncWiM0jL0jVN0IliC+2zrZ Qr8WN/nEzxQKDF1AH00wdkZcy8MjKKCx2NwWu3y6MrrD8lT2rFa6YhR4fgdv3yot hW42kyxC98rm7SjWqMgQ65EXBj5Id91Y5TjiNviiwM6Ql7B7Wg74mcFHGIckWaBV bWKfXMcTVAk6XqiZZLdOdL87FkkQqi+GdWTCXTgQ8VogQaNvdHOcFU9LXpkj7ZQF 4Z71hz2R3oQ13I+07fpIdu+tFCFTZDNx6M4FlKO2ty8p20VFMMTuvtIcQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdehgddvjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 2 May 2022 06:29:41 -0400 (EDT) From: Thomas Monjalon To: Conor Walsh Cc: john.mcnamara@intel.com, web@dpdk.org Subject: Re: [PATCH v4] update Intel roadmap for 22.07 Date: Mon, 02 May 2022 12:29:39 +0200 Message-ID: <10280950.T7Z3S40VBb@thomas> In-Reply-To: <20220425130652.4736-1-conor.walsh@intel.com> References: <20220324122439.27090-1-conor.walsh@intel.com> <20220425130652.4736-1-conor.walsh@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: web-bounces@dpdk.org I've still some doubts about some items, but this patch is pending for long, so I will adapt it with my understanding. See some questions below. Please could you reply to make things clear? 25/04/2022 15:06, Conor Walsh: > v2: > - Drop removal of "qat with OpenSSL-3.0 library" So there will be a change in qat for OpenSSL 3 ? > +- Intel IPU SoC add new "idpf" PMD > +- Intel AFU PMD based on rawdev Not clear what AFU is. Is it for the IPU above? We already have an AFU PMD raw/ifpga. > > - vhost async dequeue for split ring and enable in vhost sample app > - vhost library statistics > - virtio hash reporting > +- vhost add thread-unsafe/thread-safe in-flight packets check > +- vhost add async dequeue support for split ring This item is redundant with the first one of this section.