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 58E91A00BE; Tue, 15 Mar 2022 12:00:26 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2BC0240395; Tue, 15 Mar 2022 12:00:26 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 94B174014F for ; Tue, 15 Mar 2022 12:00:24 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BADA85C0591; Tue, 15 Mar 2022 07:00:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Tue, 15 Mar 2022 07:00:23 -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; bh=5lTBwssyog/PTx tcNDctV7xgGn0J4axwRKPCBEFpiqw=; b=XmDPY8EzWilH5/JJMf23kyehCS2ksd gI2hFe+fX7KSK7dRqJl0pXJZ3gId+HePYsLsnXSMqOLafUfbfOv5CHmC824we+oy UFzDjuDRHXZjylkTG3UZ67jci/7MrUVnKA0G13ef/fS1FsqF+QSN1kpEpYTDQ2+F nmPyDZZoBbD8U02AEFd9g4Fb8deOTrQ9Kga8USmD+O5wJXdm3zfrHzaWSG3hD8nF +Qm9uumzX+9Y1LSj1x9+iLOIzBAakSMX/zGOkgpZLSM6viLhAJHL3wFTPJZrmHfG st6j1v2taoLEyKQ6RINqrL7zxWY1NEtghjCwy9d6xeA72ngLsOSNxpPQ== 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=fm3; bh=5lTBwssyog/PTxtcNDctV7xgGn0J4axwRKPCBEFpi qw=; b=aOCOe9FxvWGaKJHhUdnBbyaxT56mILl6ku4Q8dwc2M6xPrZ31gbDX45KS wa+LKLL6QabONctFtyWipmUbWzX8MGhsj34UKlXFpu8CfIuON6QRqa/XdLqWSjtg DJqnWc+HO/OfHOv3/eyuh5is5wpHFzYYsoYW9GpIPs4caD7wWSefM9MgWNVwGMwe RMxk2xRvNpwKtcmbkvZFA1qs9FXf67K4ZjOcL17lRW/0CXS9BT1oHCVKCwPLpIws zaei7XPUH3c9oUpo9RijDMNQzq4zfZlw2Xo+RhJFOqmoBvORW78cNEq2y2q6IUr5 2BJooy76kC0i6rXgazWpLE+0cf7RA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudeftddgvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Mar 2022 07:00:21 -0400 (EDT) From: Thomas Monjalon To: "Stokes, Ian" Cc: Ilya Maximets , "Maxime Coquelin (maxime.coquelin@redhat.com)" , "Pai G, Sunil" , "Hu, Jiayu" , "ovs-dev@openvswitch.org" , "dev@dpdk.org" , Kevin Traynor , Flavio Leitner , "Mcnamara, John" , "Van Haaren, Harry" , "Ferriter, Cian" , "mcoqueli@redhat.com" , "fleitner@redhat.com" Subject: Re: OVS DPDK DSA Architecture/Design Discussion Date: Tue, 15 Mar 2022 12:00:20 +0100 Message-ID: <2144208.72vocr9iq0@thomas> In-Reply-To: <55227b9e9dcf4562a4dae8ef4c2938bf@intel.com> References: <55227b9e9dcf4562a4dae8ef4c2938bf@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 15/03/2022 11:27, Stokes, Ian: > Hi All, > > We'd like to put a public meeting in place for the stakeholders > of DPDK and OVS to discuss the next steps and design of > the DSA library along with its integration in OVS. There is no DSA library. Do you mean the IOAT driver in DPDK for the DMA library? If it is just for discussing the Intel driver, no way I attend. And even if it is for discussing the DMA library integration, I don't understand why the DPDK community is required. If there is an issue with the library API, please tell it. We need email discussions, not meeting request sent few hours in advance. Ian, I know you are not a beginner in the community, what happens?