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 1C92F2BEB for ; Thu, 4 Aug 2016 19:18:49 +0200 (CEST) Received: by mail-wm0-f52.google.com with SMTP id o80so2136956wme.1 for ; Thu, 04 Aug 2016 10:18:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=UZrjSYs47CTC6XMITCIdxnICy9nbTOzNkqPpl8wTL7s=; b=DlGkQuJidfSH9NpOcFt/XwvnScCW4YDEjqUyjNPA+D1rf8lP4mfEinlYFGB0iIJIDh GtLwkD0qeBF+FqXw9FFhpjVR2/g3oTHjJY3CfkUqtUmadABDcNxpdjkiNjUq6gMSppbG 9MgGDKe2Kq9VlXFDpjL8vKV+bFfc/y0e31S1G+dP9cNDS4vlShJVLnxbnMc1FNC1ceKR 74DaMrWU6W+FoehMOQe0W8ZVO6vnn0beGR2nMJiKEagc2gEc3rL47WOro+qHJF5urj4e psWxtgzF8UldL3aXdZCt479pvFn6m3Ay7Mlz8QxKEreU8LxaG/MIrrM2qbzLH3wmOM6D nTJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=UZrjSYs47CTC6XMITCIdxnICy9nbTOzNkqPpl8wTL7s=; b=NCXpar3Nv+J6C/MK6wzCyMLzn444p5Y+zl12qD5TYkP2fXAKY946oCcPh3OYIvlrGY fA57ZqBX+ZhftGFYuyoQmFskaCRAjwiKwNmPdDfX/PkfopFnvLEfTeYv81veO63W6++n RLSYQ7g+igGgxaatL9fb0CjzoGuBKjivxIsAWyLU2UhrZFPviBKXriJTLLUxl0EAoSxM Gpd5s7tmkrBkXss16GZSjypCXzlMdJqnISAMXQiMqsEhaAQ8aGOO8v/uqAqjEYBosjCi BJFuWEEh6sUacEEHkItXwweA74DWPA7bJ98iDzSQCYWvRp/8KApD5ILzZO8HT+vW7E3Q plRw== X-Gm-Message-State: AEkoousawLmuc4KqWrYyWjG7j/szlxNAJdghmUvI4R9zXstaJBFQw02/duZ67TgEJHCY1j/j X-Received: by 10.28.35.193 with SMTP id j184mr30003767wmj.33.1470331128826; Thu, 04 Aug 2016 10:18:48 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id r127sm4553801wmf.23.2016.08.04.10.18.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Aug 2016 10:18:47 -0700 (PDT) From: Thomas Monjalon To: =?utf-8?B?5bCP5bed5rOw5paH?= Cc: dev@dpdk.org Date: Thu, 04 Aug 2016 19:18:46 +0200 Message-ID: <1570561.Rujcl7qAGG@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" 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: Thu, 04 Aug 2016 17:18:49 -0000 2016-08-04 17:00, =E5=B0=8F=E5=B7=9D=E6=B3=B0=E6=96=87: > Hi Thomas, >=20 > I'm going to develop a NFV based carrier system with SPP because it's= able > to chain VMs in high-performance and I think it might be the best sol= ution > for service function chaining. Without ivshmem, throuput between VMs = is > largely decreased. So we are not so happy if ivshmem is obsoleted. We are not obsoleting IVSHMEM which is a QEMU feature. We are just dropping the automatic allocation of DPDK objects in the gu= est through IVSHMEM. It is a weird design that nobody really wants to maintain/redesign. If someone wants to do the required work or reimplement it differently,= it may be accepted. > As you mentioned, we can use v16.07 but it's unwelcome situation for = us and > our possible users cannot gain of improvements from future version of= DPDK. > I'm appreciated if you kindly keep ivshmem to be maintained. Nobody wants to really work on it. That's a fact, sorry. > Or, is there > any idea for high-performance inter-VM communication as ivshmem? Yes you can implement an IVSHMEM driver in DPDK. There was an attempt to do so which is also unmaintained: =09http://dpdk.org/browse/old/memnic/ I think it would be a better approach than what exists currently.