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 BB837A00BE; Tue, 15 Mar 2022 14:21:04 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 48B8640395; Tue, 15 Mar 2022 14:21:04 +0100 (CET) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by mails.dpdk.org (Postfix) with ESMTP id 779FC4014F for ; Tue, 15 Mar 2022 14:21:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1647350462; x=1678886462; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+E4QUqhWhzgt9zWrZdYVojJ49jMV9exAnoxilRrT5tI=; b=f0JlvBwRoIrQ9PollVLnjJjJBfId+jftDyPLjrHZwdOkm8km0CrIpK+T XcsWo8ZgkM6wdg1MeeMllDMmX672CNNKUs3rr5qvMJDXWVq56TBkqDe7H 42vtmwAKDeZ+P7yXSTd33Lcfu0Z7A9mjZXcSerC1pOrIU3jyBrZTbAD9l PJoHWu4yDfAIhXC/AwThRDR23oyd4E/VORkSPay6IRFZwW15Ky3a3JvpE L8nV5LVcK7ZfYLju1H2eQl8kxJbzBDZl6NibvHEeBIj56FL415WNZmldy KBOUqK0VlGFscbd00dtT7Gcat7mwKEKOot99vo7Wfj5Y88/7gW5oaSaBb w==; X-IronPort-AV: E=McAfee;i="6200,9189,10286"; a="236901125" X-IronPort-AV: E=Sophos;i="5.90,183,1643702400"; d="scan'208";a="236901125" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Mar 2022 06:21:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,183,1643702400"; d="scan'208";a="690190648" Received: from fmsmsx602.amr.corp.intel.com ([10.18.126.82]) by fmsmga001.fm.intel.com with ESMTP; 15 Mar 2022 06:21:01 -0700 Received: from shsmsx604.ccr.corp.intel.com (10.109.6.214) by fmsmsx602.amr.corp.intel.com (10.18.126.82) 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 06:21:00 -0700 Received: from fmsmsx612.amr.corp.intel.com (10.18.126.92) by SHSMSX604.ccr.corp.intel.com (10.109.6.214) 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 21:20:57 +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 06:20:56 -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: Adgz07XE2UzYbpQtSO276erSaa8QIgAADE0AATCoeQAADjdEQP//l++AgABZd4A= Date: Tue, 15 Mar 2022 13:20:55 +0000 Message-ID: <089739fa2cd946a3a2f38c0a9168fd76@intel.com> References: <55227b9e9dcf4562a4dae8ef4c2938bf@intel.com> <2144208.72vocr9iq0@thomas> <9224515f58ee465d97f02429bbc23576@intel.com> <5782175.alqRGMn8q6@thomas> In-Reply-To: <5782175.alqRGMn8q6@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 12:14, Stokes, Ian: > > > 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? > > > > Apologies Thomas, > > > > DMA-Dev library is actually what's intended to be discussed to clarify. > > Will re-send the invite with the correct title. >=20 > If you want to have a good number of attendees, > you should postpone to a later date, so we can plan in advance. > You also need to describe the problem to discuss. > That's really better to start with emails, and to have a summary > after the meeting. Agreed, we have a few people who can't make it today so will push to the sa= me time next week. I'll also update the summary of what's to be discussed. = So it's clearer. >=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. > > > > > > If there is an issue with the library API, please tell it. > > > We need email discussions, not meeting request sent few hours in adva= nce. > > > Ian, I know you are not a beginner in the community, what happens? >=20 > So if I understand well, there is no urgent problem to discuss? No Immediate issues, but from what I understand a number of designs have be= en prototyped so their results and next steps should be discussed for an ag= reed approach from both communities to allow future use and integration. Thanks Ian >=20