From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0C414C64EC4 for ; Thu, 9 Mar 2023 13:14:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229925AbjCINN6 (ORCPT ); Thu, 9 Mar 2023 08:13:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33640 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229875AbjCINN5 (ORCPT ); Thu, 9 Mar 2023 08:13:57 -0500 Received: from smtp-fw-2101.amazon.com (smtp-fw-2101.amazon.com [72.21.196.25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0E18C1EFD0 for ; Thu, 9 Mar 2023 05:13:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1678367636; x=1709903636; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=hvq1cXqD7ebK5lSGkmCeCsuYmGYiFUqJ6DTYCie7hXA=; b=ZCUSkxO9flgGOTBwb+tsq7bO1CDEZHGenhce4tKQ9DCgQUzkS7v3l7JK urTWX3hCNhTBUCa5tiVgUIzqd4ZsPVJNt6BmV9acny0QItJLnlze2HyxV OQ4aFdB8+N+lBjUbahrBcM+iwWWs2wbvA9n0iNCRMbPKNwTmLgVkzisIl k=; X-IronPort-AV: E=Sophos;i="5.98,246,1673913600"; d="scan'208";a="301249426" Received: from iad12-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-pdx-2a-m6i4x-44b6fc51.us-west-2.amazon.com) ([10.43.8.6]) by smtp-border-fw-2101.iad2.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Mar 2023 13:13:51 +0000 Received: from EX19D011EUA001.ant.amazon.com (pdx1-ws-svc-p6-lb9-vlan2.pdx.amazon.com [10.236.137.194]) by email-inbound-relay-pdx-2a-m6i4x-44b6fc51.us-west-2.amazon.com (Postfix) with ESMTPS id DF6DFA0351; Thu, 9 Mar 2023 13:13:49 +0000 (UTC) Received: from EX19D028EUB003.ant.amazon.com (10.252.61.31) by EX19D011EUA001.ant.amazon.com (10.252.50.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.24; Thu, 9 Mar 2023 13:13:48 +0000 Received: from u570694869fb251.ant.amazon.com (10.85.143.174) by EX19D028EUB003.ant.amazon.com (10.252.61.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.24; Thu, 9 Mar 2023 13:13:41 +0000 From: Shay Agroskin To: David Miller , Jakub Kicinski , CC: Shay Agroskin , "Woodhouse, David" , "Machulsky, Zorik" , "Matushevsky, Alexander" , Saeed Bshara , "Wilson, Matt" , "Liguori, Anthony" , "Bshara, Nafea" , "Belgazal, Netanel" , "Saidi, Ali" , "Herrenschmidt, Benjamin" , "Kiyanovski, Arthur" , "Dagan, Noam" , "Arinzon, David" , "Itzko, Shahar" , "Abboud, Osama" Subject: [PATCH v4 net-next 0/5] Add tx push buf len param to ethtool Date: Thu, 9 Mar 2023 15:13:14 +0200 Message-ID: <20230309131319.2531008-1-shayagr@amazon.com> X-Mailer: git-send-email 2.30.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.85.143.174] X-ClientProxiedBy: EX19D044UWA002.ant.amazon.com (10.13.139.11) To EX19D028EUB003.ant.amazon.com (10.252.61.31) Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Changes since v3: - Removed RFC tag and added a Jakub's signoff on one of the first patch Changes since v2: - Added a check that the driver advertises support for TX push buffer instead of defaulting the response to 0. - Moved cosmetic changes to their own commits - Removed usage of gotos which goes against Linux coding style - Make ENA driver reject an attempt to configure TX push buffer when it's not supported (no LLQ is used) Changes since v1: - Added the new ethtool param to generic netlink specs - Dropped dynamic advertisement of tx push buff support in ENA. The driver will advertise it for all platforms This patchset adds a new sub-configuration to ethtool get/set queue params (ethtool -g) called 'tx-push-buf-len'. This configuration specifies the maximum number of bytes of a transmitted packet a driver can push directly to the underlying device ('push' mode). The motivation for pushing some of the bytes to the device has the advantages of - Allowing a smart device to take fast actions based on the packet's header - Reducing latency for small packets that can be copied completely into the device This new param is practically similar to tx-copybreak value that can be set using ethtool's tunable but conceptually serves a different purpose. While tx-copybreak is used to reduce the overhead of DMA mapping and makes no sense to use if less than the whole segment gets copied, tx-push-buf-len allows to improve performance by analyzing the packet's data (usually headers) before performing the DMA operation. The configuration can be queried and set using the commands: $ ethtool -g [interface] # ethtool -G [interface] tx-push-buf-len [number of bytes] This patchset also adds support for the new configuration in ENA driver for which this parameter ensures efficient resources management on the device side. David Arinzon (1): net: ena: Add an option to configure large LLQ headers Shay Agroskin (4): ethtool: Add support for configuring tx_push_buf_len net: ena: Make few cosmetic preparations to support large LLQ net: ena: Recalculate TX state variables every device reset net: ena: Add support to changing tx_push_buf_len Documentation/netlink/specs/ethtool.yaml | 8 + Documentation/networking/ethtool-netlink.rst | 43 +-- drivers/net/ethernet/amazon/ena/ena_eth_com.h | 4 + drivers/net/ethernet/amazon/ena/ena_ethtool.c | 57 +++- drivers/net/ethernet/amazon/ena/ena_netdev.c | 259 +++++++++++------- drivers/net/ethernet/amazon/ena/ena_netdev.h | 15 +- include/linux/ethtool.h | 14 +- include/uapi/linux/ethtool_netlink.h | 2 + net/ethtool/netlink.h | 2 +- net/ethtool/rings.c | 33 ++- 10 files changed, 313 insertions(+), 124 deletions(-) -- 2.25.1