From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f172.google.com (mail-pf0-f172.google.com [209.85.192.172]) by dpdk.org (Postfix) with ESMTP id 3B0587D52 for ; Wed, 23 Aug 2017 17:31:47 +0200 (CEST) Received: by mail-pf0-f172.google.com with SMTP id c28so1465062pfe.3 for ; Wed, 23 Aug 2017 08:31:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=RVDuS5lpS2FIIvn2l+4ExOl/CypaDeYpMMzBw4ce3fw=; b=cwpTZJ8YODS90KjlJ+FqJuKpcdyli5oavf/nMHSbvBzHcepkgxihnksoe4wOuhIiP+ OKkLKDBh8oUdioth9Dn0Bz/l0P3g+0DG40egw61dyd9Q5f/ExLfP4bGvzWsH9xIN3917 0/YrCIaSokR5ZSwNkFDemrYyX5mz9QKlRHkoTOiY0ztYs+Y8RI/eDyp48cieE+bhdu+b 6G+FFWvdZZSBEtsbMjutZvpsP0L9w6M4MYsnqBBdshur1Sgp53WwTkqaIPtlNwqVABLu LpiXZjQt7o/Je5nKoF2Pei+kyRbfpS5OkaKpk0l7bqWG+Zy2UdAi2COrP46THKgV9+zl plNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=RVDuS5lpS2FIIvn2l+4ExOl/CypaDeYpMMzBw4ce3fw=; b=ajB7ghjXXCKG8jVsAcz2zViaXc+0vEcQU5nfM2d1n5b8+pXUEoMXvXQeXUaInDyKq5 zLnm28XDxPiTgiGoEvFDxcMo1nXiOX0gV7XpqoMY1jcoZuyRGi4GLOqEBuBs3PdPbdqq txkWqv5Co3r87Gyky/P6ikHkB7tbDvmPHQ0/PHaNP10FLWujuo8SI+tdTXnMzEEqXx8r 0IpxCjxiRgrYIZ8nV+TPJCSMbz1BIo5dcs153HRihVEIDzp8VDHqaJOohynYo6sjxeff lebjC2PZFod9oQ/ACxTxMPlxGGNH12gLwTQNsJQuXK/b8SIQ+jTNxucYNd9SEE0rGvky jqwQ== X-Gm-Message-State: AHYfb5jTqJUyvIqkBJdl1FFAIOZgkmx/MBcluX1/eA7I3xe1CduvjQEw VzoUxej9Hrv/wsmE9fEycQ== X-Received: by 10.84.233.204 with SMTP id m12mr3429688pln.72.1503502306325; Wed, 23 Aug 2017 08:31:46 -0700 (PDT) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id t18sm3856363pfj.9.2017.08.23.08.31.45 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 23 Aug 2017 08:31:45 -0700 (PDT) Date: Wed, 23 Aug 2017 08:31:35 -0700 From: Stephen Hemminger To: Olivier MATZ Cc: Yuanhan Liu , maxime.coquelin@redhat.com, dev@dpdk.org, stable@dpdk.org Message-ID: <20170823083135.67193f91@xeon-e3> In-Reply-To: <20170823093025.bhjwbygfyz4ifd6r@glumotte.dev.6wind.com> References: <20170707195250.22259-1-stephen@networkplumber.org> <20170708031222.GA11626@yliu-home> <20170823093025.bhjwbygfyz4ifd6r@glumotte.dev.6wind.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 0/2] virtio fix false offload claims X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2017 15:31:47 -0000 On Wed, 23 Aug 2017 11:30:26 +0200 Olivier MATZ wrote: > Hello, > > On Sat, Jul 08, 2017 at 11:12:22AM +0800, Yuanhan Liu wrote: > > On Fri, Jul 07, 2017 at 12:52:48PM -0700, Stephen Hemminger wrote: > > > While doing code for Hyper-V, noticed that the virtio driver was > > > confused about receive versus transmit offloads. The virtio > > > checksum offload is L4 (TCP/UDP) only, not IPv4. Also, TSO > > > and LRO are not the same. > > > > > > This may break some program that was assuming it was getting offloads > > > that it wasn't. > > > > Applied to dpdk-next-virtio. > > > > And I think they should be backported to stable releases, thus, > > > > Cc: stable@dpdk.org > > > > Thanks. > > > > --yliu > > > > > > Stephen Hemminger (2): > > > virtio: don't falsely claim to do IP checksum > > > virtio: don't claim to support LRO > > > > > > drivers/net/virtio/virtio_ethdev.c | 30 +++++------------------------- > > > 1 file changed, 5 insertions(+), 25 deletions(-) > > > > > > -- > > > 2.11.0 > > I think these 2 commits break the virtio offload, which can be tested as > described in this test plan: > http://dpdk.org/ml/archives/dev/2016-October/048092.html > > First, about checksum: the description of rxmode->hw_ip_checksum is: > > hw_ip_checksum : 1, /**< IP/UDP/TCP checksum offload enable. */ > > So, while I agree the name is not well chosen, it is valid to set it > for virtio to enable L4 checksum. > > Then about LRO: setting rxmode->enable_lro is a way to tell the host that the > guest is ok to receive tso packets. From the guest point of view, it is like > enabling lro on a physical driver. Again, it is valid and useful to do this. > > Before removing these features, it would have been nice to have a quick look at > the commits that introduced them. I am ok with keeping LRO as long as the documentation changed. And virtio driver did some enforcement. For checksums, the hw_ip_checksum flag either needs to be more fine grain (IP, UDP, TCP) which would be best, or virtio would have to check IP checksum in software.