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 DA5E6A00BE; Tue, 15 Mar 2022 12:14:42 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6DC4F40395; Tue, 15 Mar 2022 12:14:42 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mails.dpdk.org (Postfix) with ESMTP id D2DFA4014F for ; Tue, 15 Mar 2022 12:14:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1647342881; x=1678878881; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=4+VYDURuY//zEU6w/zystQR9Ms/1mIbZ9HdjnHd5OFQ=; b=ZE4aNYeNiEDlFvaJLsNhMNFByswupmwGvLB39MwiwGQA/Ps3nZhD5f2R gZaR2y7GcZEGv+XN7XimQXPWtkZVEhUSo+AB/j2ls7dC9OIdqeII/552+ 3uwxAODKW8DNrpqJAOD6vCtuOyqw/iEEa9a/KNd1NdtPPPA8LjANIKWg1 twb0H0JmYLE65lHcK+NagDIkncDxa3z+xsy5ImtA9lSyY6UEer8krcn4N CVSbsQXhq0t2u3YCwybZ8N9s5E5sOVYtrTZHCT/LIPu66a4VTnA01HN8c LihleGIeeMZFcrzWhOy/anacL2I49c5Fprc/lf3iFlc8cb9qp2l3eeIE6 A==; X-IronPort-AV: E=McAfee;i="6200,9189,10286"; a="256463062" X-IronPort-AV: E=Sophos;i="5.90,183,1643702400"; d="scan'208";a="256463062" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Mar 2022 04:14:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,183,1643702400"; d="scan'208";a="515824505" Received: from fmsmsx604.amr.corp.intel.com ([10.18.126.84]) by orsmga006.jf.intel.com with ESMTP; 15 Mar 2022 04:14:39 -0700 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) by fmsmsx604.amr.corp.intel.com (10.18.126.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Tue, 15 Mar 2022 04:14:38 -0700 Received: from fmsmsx612.amr.corp.intel.com (10.18.126.92) by SHSMSX603.ccr.corp.intel.com (10.109.6.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Tue, 15 Mar 2022 19:14:35 +0800 Received: from fmsmsx612.amr.corp.intel.com ([10.18.126.92]) by fmsmsx612.amr.corp.intel.com ([10.18.126.92]) with mapi id 15.01.2308.021; Tue, 15 Mar 2022 04:14:33 -0700 From: "Stokes, Ian" To: Thomas Monjalon 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 Thread-Topic: OVS DPDK DSA Architecture/Design Discussion Thread-Index: Adgz07XE2UzYbpQtSO276erSaa8QIgAADE0AATCoeQAADjdEQA== Date: Tue, 15 Mar 2022 11:14:33 +0000 Message-ID: <9224515f58ee465d97f02429bbc23576@intel.com> References: <55227b9e9dcf4562a4dae8ef4c2938bf@intel.com> <2144208.72vocr9iq0@thomas> In-Reply-To: <2144208.72vocr9iq0@thomas> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-product: dlpe-windows dlp-version: 11.6.401.20 x-originating-ip: [163.33.253.164] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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. >=20 > There is no DSA library. > Do you mean the IOAT driver in DPDK for the DMA library? Apologies Thomas, DMA-Dev library is actually what's intended to be discussed to clarify. Wil= l re-send the invite with the correct title. Thanks Ian >=20 > 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. >=20 > 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? >=20