Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3733548ybl; Mon, 13 Jan 2020 01:31:42 -0800 (PST) X-Google-Smtp-Source: APXvYqwPR6kDQTTioR7VrrYLviJh1Tg86cl7XlZPdu4nLvs5al64NK5HuPpr6EdNS2zkSGsyySZT X-Received: by 2002:a9d:1c95:: with SMTP id l21mr12263237ota.271.1578907902325; Mon, 13 Jan 2020 01:31:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578907902; cv=none; d=google.com; s=arc-20160816; b=S6dECcp9TV0TWGKBZYTeQK9tMwH7rmIdumC6hh63+n72t0eD9m+QVjHHzUuFZwpPlb faE3THl8l9YQ8gV+Eeb4O17tuEOXvDSkxEQ0XQDs1/JwPhc+CjOYgYwEx8CD3Md9u9cJ TDdxM/Pivmkav3wlFR1Ai8JLN/n3zgBY/vemUwxdRRMmHwqSJxYUjXOk6nEoMlMLUpJK Ld/6tQwuA9zw9HEwmUnaHwx4T2owcm9ndGAAfaeAp7OvuX6CQ5L/Bc9JZC/HxJI1S8Hv aPiNbrVlYLO/wP/28fatTx/THHvrlEkQSYCcKt4FtzbCxhkTfGKFI7RUSZfYTFyztlfi cEhg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:user-agent:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-filter:dkim-signature:dkim-filter; bh=ay0aQdubfRd2z0EzjvG25Fck9nkLxv3o/IS7a8ekqDc=; b=sjTxwc58PiIrO9O9TF8ImX3Torp+n1K0Qs0r+aL/miFtdSaSM6umqN+GXHsoK1Dh7/ P3CqKDW/9vP2NhE+LKiKLMEnREhhwEf2rSSvGn6zv3kOh9en4SniMMs/hlQ0SlMSyAts qbRojOmF2An5fRvFIkmS81M5Ykw0PTTH4+yTk6qnsX8cUURXLAG498NJjKhLphMu1G58 TcNcfzKZIBzCGQkZFkIQOsG5Ts/njaBCSRxKIv6imo6dZ0EXWhJ2B5lrYB+1rYnaWc0Z QM64oEexZpBhQsdtmt51voV7UbeyqC0K3SkdLzBG8gtGEz2uQGR0fYiNK6e8bJIfUfQF 6dpw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@dlink.ru header.s=mail header.b=bGqnuwxb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t23si6314023otk.304.2020.01.13.01.31.30; Mon, 13 Jan 2020 01:31:42 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@dlink.ru header.s=mail header.b=bGqnuwxb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728734AbgAMJaY (ORCPT + 99 others); Mon, 13 Jan 2020 04:30:24 -0500 Received: from fd.dlink.ru ([178.170.168.18]:52132 "EHLO fd.dlink.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725992AbgAMJaX (ORCPT ); Mon, 13 Jan 2020 04:30:23 -0500 Received: by fd.dlink.ru (Postfix, from userid 5000) id D580E1B214D6; Mon, 13 Jan 2020 12:30:20 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 fd.dlink.ru D580E1B214D6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dlink.ru; s=mail; t=1578907820; bh=ay0aQdubfRd2z0EzjvG25Fck9nkLxv3o/IS7a8ekqDc=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=bGqnuwxbo0Z07sOYtv9NUXBctnRgbn7nlabKLezk3u4M46bLYz7z9E6ySDnUpTWMZ Ezwe/0ZWB6UgSVedSes8EerOVLi70PFeujrQSEqsZJjOB/rMRcy+0gc9E7jce0wj47 gC4dSYDAHBLi17t9IhWDm9gDK7btRMzc9ex8AXt0= X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.dlink.ru X-Spam-Level: X-Spam-Status: No, score=-99.2 required=7.5 tests=BAYES_50,URIBL_BLOCKED, USER_IN_WHITELIST autolearn=disabled version=3.4.2 Received: from mail.rzn.dlink.ru (mail.rzn.dlink.ru [178.170.168.13]) by fd.dlink.ru (Postfix) with ESMTP id CCEA41B20968; Mon, 13 Jan 2020 12:30:07 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 fd.dlink.ru CCEA41B20968 Received: from mail.rzn.dlink.ru (localhost [127.0.0.1]) by mail.rzn.dlink.ru (Postfix) with ESMTP id 2FC251B2613E; Mon, 13 Jan 2020 12:30:07 +0300 (MSK) Received: from mail.rzn.dlink.ru (localhost [127.0.0.1]) by mail.rzn.dlink.ru (Postfix) with ESMTPA; Mon, 13 Jan 2020 12:30:07 +0300 (MSK) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 13 Jan 2020 12:30:06 +0300 From: Alexander Lobakin To: Vladimir Oltean Cc: "David S. Miller" , Edward Cree , Andrew Lunn , Vivien Didelot , Florian Fainelli , Hauke Mehrtens , Sean Wang , Matthias Brugger , Jiri Pirko , Eric Dumazet , Paolo Abeni , Jakub Kicinski , Taehee Yoo , Stephen Hemminger , Stanislav Fomichev , Daniel Borkmann , Song Liu , Matteo Croce , Jakub Sitnicki , Paul Blakey , Yoshiki Komachi , netdev , lkml , linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH RFC net-next 00/20] net: dsa: add GRO support In-Reply-To: References: <20191230143028.27313-1-alobakin@dlink.ru> User-Agent: Roundcube Webmail/1.4.0 Message-ID: <607283965483d3bc3c0e969b1fadf540@dlink.ru> X-Sender: alobakin@dlink.ru Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Vladimir Oltean wrote 31.12.2019 18:32: > Hi Alexander, Hi, > On Mon, 30 Dec 2019 at 16:31, Alexander Lobakin > wrote: >> >> I mark this as RFC, and there are the key questions for maintainers, >> developers, users etc.: >> - Do we need GRO support for DSA at all? >> - Which tagger protocols really need it and which don't? >> - Does this series bring any performance improvements on the >> affected systems? > > If these are these questions for maintainers, developers, users etc, > then what has determined you to make these changes? The main reason was obviously pretty good results on a particular hardware on which I developed this (and other) series and a general opinion that GRO improves overall performance on most systems. DSA is a special case though. > Thanks, > -Vladimir Regards, ᚷ ᛖ ᚢ ᚦ ᚠ ᚱ