From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=MCu7gU8Io7LnUyr0YMfIQe9L0z4gF9DD6S/kIHFaQyw=; b=0YO7NGwn3j+cFTh6m/fuTcT5VHj7u1AHlGVK/XfnLmdOOnlXOi8u5rt6fdHDc6uJU3 5rDMmfvhh78q7j/e0C3eRmHPcBye4RzpbuD/t9ik21ZNvUGNat/7N0zMMoJUStpvAOcK y6UoKmnYmCr6hNb11EAeu6xVSKIZp/cMTAMs3nCCwn+X7hqmijyHSCBGGnLlFeMN6bnA G4QC39yPzlhDVfX5/8Ra9JFC7ftR6HIwSaPZlVTJ55t86EYwbA6PYlkaSHYWmxPpu+Zq uFsBrgZYjlHp13QStyIzJBOLgnOz2czKdgmSy7G7T43nLRf2jA/T+LAiXkGgDPOY7x/4 Tidw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=MCu7gU8Io7LnUyr0YMfIQe9L0z4gF9DD6S/kIHFaQyw=; b=IezWk5Ki1Xaq4ASFE/hk5qRQA0xRKakW8JiDCAkhAO9K7ukuLkrxg5R37jdwuyVdhQ XXyn7ZvoEq86g+ZvD9v3PbxqCfq9GhimgpCZZyv8C1vGjUojL1frHY8Hzzi8zXKrYy/N IVJ+KwKb5qJHZZJYCD27AP3TLecotRxQn2PY2Fged/TXJ07deNTrF1+yMzWagvpdxx1k p8jZYhL2aXxQRtuxyXKbHGPgBuznMO5hE0V87JZSfPRInrYRD/i4bfOKWAnH22egNpk7 UPRz8wTtHMpsBhhCdHPf5Mavp41Pn+4RQ4l5NZJS2E+ivq2MH9p/4NuEAHoGQjubo1mj CsUw== X-Gm-Message-State: AEkoousKEKfHxl2+fZ9EQTGJyANsbDy7yjSbikTntuTqwmN4BfqcfQeWjzymDQysA6Q8abt3 X-Received: by 10.28.152.5 with SMTP id a5mr3746496wme.76.1469173922343; Fri, 22 Jul 2016 00:52:02 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id r67sm11009581wmb.14.2016.07.22.00.52.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jul 2016 00:52:01 -0700 (PDT) Date: Fri, 22 Jul 2016 00:52:01 -0700 (PDT) X-Google-Original-Date: Fri, 22 Jul 2016 09:52 +0200 From: Thomas Monjalon To: Hiroshi Shimamoto Cc: "anatoly.burakov@intel.com" , dev@dpdk.org Message-ID: <1627928.Urc8at9buT@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD0602E280@BPXM14GP.gisp.nec.co.jp> References: <1469032546-6256-1-git-send-email-thomas.monjalon@6wind.com> <7F861DC0615E0C47A872E6F3C5FCDDBD0602E280@BPXM14GP.gisp.nec.co.jp> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] 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: Fri, 22 Jul 2016 07:52:02 -0000 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.