From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fm2nodo1.polito.it (fm2nodo1.polito.it [130.192.180.12]) by dpdk.org (Postfix) with ESMTP id 79B832B91 for ; Thu, 28 Jul 2016 17:23:36 +0200 (CEST) Received: from polito.it (frontmail2.polito.it [130.192.180.42]) by fm2nodo1.polito.it with ESMTP id u6SFNYo1005618-u6SFNYo3005618 (version=TLSv1.0 cipher=DHE-RSA-AES256-SHA bits=256 verify=CAFAIL); Thu, 28 Jul 2016 17:23:34 +0200 Received: from [130.192.225.241] (account d040768@polito.it [130.192.225.241] verified) by polito.it (CommuniGate Pro SMTP 6.1.9) with ESMTPSA id 50828583; Thu, 28 Jul 2016 17:23:34 +0200 To: Christian Ehrhardt , Jan Viktorin References: <1469032546-6256-1-git-send-email-thomas.monjalon@6wind.com> <20160727210841.6dec9ef3@pcviktorin.fit.vutbr.cz> Cc: Thomas Monjalon , anatoly.burakov@intel.com, dev From: Mauricio Vasquez Message-ID: <064a4109-711b-8377-53aa-f6c25236bf09@polito.it> Date: Thu, 28 Jul 2016 17:23:34 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-FEAS-SYSTEM-WL: 130.192.180.42 Subject: Re: [dpdk-dev] doc: announce ivshmem support removal X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2016 15:23:36 -0000 Hello All, Here in Politecnico di Torino we use the ivshmem technology from a research point of view. Our research efforts focus in optimizing the inter-Virtual Network Function communication, currently we have implemented two versions of our prototype, they are described in [1] and [2]. Unfortunately, we do not have the human resources to implement the improvements that are necessary for ivshmem in DPDK, however we could provide some feedback and testing for possible patches. Best Regards, Mauricio Vasquez. [1] https://www.researchgate.net/publication/305699120_Transparent_Optimization_of_Inter-Virtual_Network_Function_Communication_in_Open_vSwitch [2] https://www.researchgate.net/publication/305699122_A_Transparent_Highway_for_inter-Virtual_Network_Function_Communication_with_Open_vSwitch On 07/28/2016 11:20 AM, Christian Ehrhardt wrote: > Hi Thomas, > just my two cents as Ubuntu DPDK maintainer (and part of the Debian Team > that does the same). > (It seems I can reuse that line for all posts about the deprecation notices > :-) ) > > While IVSHMEM was enabled (as it was the default) I never heard of any > users of what we provided so far. > But that is expected considering that not all qemu bits are landed either. > Since it will follow the process of "deprecation notice -> grace period -> > ABI bump" on removal, I think packaging and consuming applications should > be fine. > > I'd agree to Hiroshi that, if really needed a clean re-implementation more > properly separated from EAL likely is the best way to go. > > I think it is a good change to drop rather complex code in favor of > stabilizing the main paths: > Acked-by: Christian Ehrhardt > > > Christian Ehrhardt > Software Engineer, Ubuntu Server > Canonical Ltd > > On Wed, Jul 27, 2016 at 9:08 PM, Jan Viktorin > wrote: > >> On Wed, 20 Jul 2016 18:35:46 +0200 >> Thomas Monjalon wrote: >> >>> There was a prior call with an explanation of what needs to be done: >>> http://dpdk.org/ml/archives/dev/2016-June/040844.html >>> - Qemu patch upstreamed >>> - IVSHMEM PCI device managed by a PCI driver >>> - No DPDK objects (ring/mempool) allocated by EAL >>> >>> As nobody seems interested, it is time to remove this code which >>> makes EAL improvements harder. >>> >>> Signed-off-by: Thomas Monjalon >>> Acked-by: David Marchand >>> Acked-by: Maxime Coquelin >> Acked-by: Jan Viktorin >