From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] doc: announce ivshmem support removal Date: Fri, 22 Jul 2016 00:52:01 -0700 (PDT) Message-ID: <1627928.Urc8at9buT@xps13> References: <1469032546-6256-1-git-send-email-thomas.monjalon@6wind.com> <7F861DC0615E0C47A872E6F3C5FCDDBD0602E280@BPXM14GP.gisp.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: "anatoly.burakov@intel.com" , dev@dpdk.org To: Hiroshi Shimamoto Return-path: Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com [74.125.82.52]) by dpdk.org (Postfix) with ESMTP id 92F863777 for ; Fri, 22 Jul 2016 09:52:02 +0200 (CEST) Received: by mail-wm0-f52.google.com with SMTP id o80so53601463wme.1 for ; Fri, 22 Jul 2016 00:52:02 -0700 (PDT) In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD0602E280@BPXM14GP.gisp.nec.co.jp> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-07-22 00:36, Hiroshi Shimamoto: > Hi, > > > Subject: [dpdk-dev] [PATCH] doc: announce ivshmem support removal > > > > 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. > > I'd like to confirm about the issue. > I know there are real users who rely on ivshmem mechanism. e.g. spp user. > Unfortunately they don't prefer to expose their opinion to the community. > Furthermore they may not have noticed this situation. These secret users can use the version 16.07. > Anyway, it is the issue that the current ivshmem implementation breaks > EAL framework and is much complicated, right? > IIUC, for DPDK, ivshmem support module should be separated from a middle of > EAL code and make it as a PCI driver. That means the current rte_ivshmem > removal should happen. To keep the functionality to share DPDK objects > between host and guest in shared memory like ivshmem, it should be > implemented cleanly. > Is my understanding correct? Yes You just forgot the need for a patch on Qemu.