Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp179775ybl; Mon, 12 Aug 2019 14:07:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqxA68fv0hH7qudWsVH15ciWOEepbOOm/5bqSZVuvNxNiCRm9r///ZYbQ8etaI8rbBLFsuQE X-Received: by 2002:a63:6eca:: with SMTP id j193mr31125383pgc.74.1565644056956; Mon, 12 Aug 2019 14:07:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565644056; cv=none; d=google.com; s=arc-20160816; b=PCmsBoYhcFwqMsSnV3DtWja2V5a/KtrDU+i8+Jitf71jta85bcS1qOnxhwdcwcw8yy xbZGSpw4LJnGA/mLo9dOUYaPxFYh/KfyINBdE0zP3Z9SSA0aibMfwayf1RHZ+xlj+r8Q Wb0XYruFqmtI9YynsicQo+1QOkZHYbI+L81JiVGOxlyYZDpyFpw/oBH4ltdcDdW51WnN vdw6P14Pa1RVz8KQVXEf4wTxv0gpjjHQsG1bbXgGmUa13z+E/BGcZ5CvWT1GEI285+HB 2yKtliniRnID9qtdpCYZy8XGZfeE8fTG1aHEDyrEeYUrOjv0uI3bagQgCYATVyZq4Xzn tzkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=myBL58iT17IIysgAH6YNBkI4QtCEgYh8UdUvfSb5Jt4=; b=sNdsrKQpX7en9tT+fVJCrVnt7t/L5jTdRg2XQ9yWl1M40VtF62FKe/x7CEkzNXJq4L PGhYgt06vFYV+gGnCA9m6L3N1XY1AtZD1Wtxj7u7Y+K5D/lMZgpnk2HuO7RED0RF5zto zCGH74e1TqYQb5B9U0gU+HHMLpd+do+1mth1/gFJ00566mLgPGEwkHMftrhMYmFfmmh1 5Js7ImUAApYqI/Ac/iNLe/rxsmkpuucIcPWCyT9shreuy0Pia9Q8h30jWrvOHLZdOxqn jf+gBxPbHsXvZJNJ+xVWkCBuVoh7ZKKriIjGp+ahRrG5Xky6giKzLLftRipkrq6J2YMJ V2Nw== ARC-Authentication-Results: i=1; mx.google.com; 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 p8si56589636plq.53.2019.08.12.14.07.21; Mon, 12 Aug 2019 14:07:36 -0700 (PDT) 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; 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 S1727145AbfHLVGU (ORCPT + 99 others); Mon, 12 Aug 2019 17:06:20 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:51310 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726757AbfHLVGT (ORCPT ); Mon, 12 Aug 2019 17:06:19 -0400 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::d71]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 28173154D32CB; Mon, 12 Aug 2019 14:06:19 -0700 (PDT) Date: Mon, 12 Aug 2019 14:06:18 -0700 (PDT) Message-Id: <20190812.140618.1288127671943783439.davem@davemloft.net> To: Jose.Abreu@synopsys.com Cc: netdev@vger.kernel.org, Joao.Pinto@synopsys.com, peppe.cavallaro@st.com, alexandre.torgue@st.com, mcoquelin.stm32@gmail.com, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next v2 04/12] net: stmmac: Add Split Header support and enable it in XGMAC cores From: David Miller In-Reply-To: <6279e35421e17256ac023227ec8cd5c8498d34d0.1565602974.git.joabreu@synopsys.com> References: <6279e35421e17256ac023227ec8cd5c8498d34d0.1565602974.git.joabreu@synopsys.com> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Mon, 12 Aug 2019 14:06:19 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jose Abreu Date: Mon, 12 Aug 2019 11:44:03 +0200 > - Add performance info (David) Ummm... Whilst cpu utilization is interesting, I might be mainly interested in how this effects "networking" performance. I find it very surprising that it isn't obvious that this is what I wanted. Do you not do performance testing on the networking level when you make fundamental changes to how packets are processed by the hardware/driver?