Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp3548618rwi; Wed, 12 Oct 2022 03:46:53 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6vgFcmyyNyphr/yzLXioH62g71A0gzYbU17i0/iw6ysWcZI5DBB/Y5DxCqAsdIkL35l/Bs X-Received: by 2002:a17:902:ecd2:b0:183:7b19:eb8c with SMTP id a18-20020a170902ecd200b001837b19eb8cmr9545802plh.11.1665571613135; Wed, 12 Oct 2022 03:46:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665571613; cv=none; d=google.com; s=arc-20160816; b=T8CKER/2ddGfcAq46XZ3ccSpXF+V6A1lQEKM+D4JHJIwWzZHStMULJmMkToQ4Kqrnb ZRKCkf4ikuoQfrQafXkMy+N5gGMxKhawLyqctgjGjs69OHisqAJQ5Rkp8lbHm3APKpTt 7NyHX9+bp4wZe4RM/RBYH7gC6SRIn+OjMlIX3onGR7FDwUO610KIaTL3K03mMTpDnjP1 SlAIQ25ezNASV3dosPNbnWmZSVUR8jeAH2jwI9otx7kx8zIL8gFvJDnqfSByKWmrmnoy U2ttW+gQWvxIE7OfAX8A6N/BFbBeXwz7NdsUTkSa1fIm0o0sDvHWX7QfTDF7s8T0R0+T sivA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:dkim-signature:date; bh=MQ9rZIoWXU894RalXxEe5qRg+Q/4BMs+ckCLyACwqOc=; b=ZxX5ZWpTtLIJyqPA86T4itS34Ct8t312a1xRPwdijC5Tqf/joYv52kAMOnkITJg385 Urt5gu3Vi+E2st1dwD68yCLGrKwTFnsMoLzJcUscwK3VTlpHlxP2virHUoZwS3rpgzG4 LeHfxgCHyijI2N20GRJREFEIABWndMbBWiHk+uT6UR3dGykJV22bVxh+ko0u33J534xY tfZ2H7ajLnuUXNKNok0gwLbcHvhhPEpkM8y8g5oqXMPgXJzPvOT6haW2oKMJmzRyPtGl fj55kZLYepPdK3ETeaaaeztHgFRsGwP0w3o478LwrmAn7X8i0ACwi+qshDkDg2G/uWMP 8XxA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b=HhLjQvNj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w27-20020a63161b000000b004525a153e80si18144281pgl.445.2022.10.12.03.46.40; Wed, 12 Oct 2022 03:46:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b=HhLjQvNj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229650AbiJLKcX (ORCPT + 99 others); Wed, 12 Oct 2022 06:32:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38370 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229567AbiJLKcV (ORCPT ); Wed, 12 Oct 2022 06:32:21 -0400 Received: from out2.migadu.com (out2.migadu.com [IPv6:2001:41d0:2:aacc::]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 57D941004B; Wed, 12 Oct 2022 03:32:20 -0700 (PDT) Date: Wed, 12 Oct 2022 18:32:10 +0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1665570738; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MQ9rZIoWXU894RalXxEe5qRg+Q/4BMs+ckCLyACwqOc=; b=HhLjQvNj0O28zE8xYD2rlR8EMG26cveb3UZCdyMn2TUuJojfWGYnfO806MEf+FjRjUglys WeN/vhNZ0kWD/NVrrU0UXnr964IBJb/PrNKY66NzhiNwLsTOZ6Vx7Jkzo9cmGMt8xbihJm 74CTovCE836uptkvtyihc3PpQAN7Ox4= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Cai Huoqing To: shaozhengchao Cc: leonro@nvidia.com, caihuoqing , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Qiao Ma , Christophe JAILLET , "Gustavo A. R. Silva" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] net: hinic: Update the range of MTU from 256 to 9600 Message-ID: <20221012103210.GA3055@chq-T47> References: <20221012082945.10353-1-cai.huoqing@linux.dev> <15f63fd8-0f0e-26bc-c74e-fc7666c6ff88@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <15f63fd8-0f0e-26bc-c74e-fc7666c6ff88@huawei.com> X-Migadu-Flow: FLOW_OUT X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12 10月 22 17:25:21, shaozhengchao wrote: > > > On 2022/10/12 16:29, Cai Huoqing wrote: > > From: caihuoqing > > > > Hinic hardware only support MTU from 256 to 9600, so set > > the max_mtu and min_mtu. > > > > And not need to add the validity judgment when set mtu, > > because the judgment is made in net/core: dev_validate_mtu > > > > Signed-off-by: caihuoqing > > --- > > drivers/net/ethernet/huawei/hinic/hinic_dev.h | 3 +++ > > drivers/net/ethernet/huawei/hinic/hinic_main.c | 3 ++- > > drivers/net/ethernet/huawei/hinic/hinic_port.c | 17 +---------------- > > 3 files changed, 6 insertions(+), 17 deletions(-) > > > > diff --git a/drivers/net/ethernet/huawei/hinic/hinic_dev.h b/drivers/net/ethernet/huawei/hinic/hinic_dev.h > > index a4fbf44f944c..2bbc94c0a9c1 100644 > > --- a/drivers/net/ethernet/huawei/hinic/hinic_dev.h > > +++ b/drivers/net/ethernet/huawei/hinic/hinic_dev.h > > @@ -22,6 +22,9 @@ > > #define LP_PKT_CNT 64 > > +#define HINIC_MAX_MTU_SIZE 9600 Hi Shao, thanks for your reply. I will change it in patch v2, like "#define HINIC_MAX_MTU_SIZE (HINIC_MAX_JUMBO_FRAME_SIZE - ETH_HLEN - ETH_FCS_LEN)" to compatible the old firmware (maybe some old cards). > > +#define HINIC_MIN_MTU_SIZE 256 > > + > > enum hinic_flags { > > HINIC_LINK_UP = BIT(0), > > HINIC_INTF_UP = BIT(1), > > diff --git a/drivers/net/ethernet/huawei/hinic/hinic_main.c b/drivers/net/ethernet/huawei/hinic/hinic_main.c > > index c23ee2ddbce3..41e52f775aae 100644 > > --- a/drivers/net/ethernet/huawei/hinic/hinic_main.c > > +++ b/drivers/net/ethernet/huawei/hinic/hinic_main.c > > @@ -1189,7 +1189,8 @@ static int nic_dev_init(struct pci_dev *pdev) > > else > > netdev->netdev_ops = &hinicvf_netdev_ops; > > - netdev->max_mtu = ETH_MAX_MTU; > > + netdev->max_mtu = HINIC_MAX_MTU_SIZE; > > + netdev->min_mtu = HINIC_MIN_MTU_SIZE; > > nic_dev = netdev_priv(netdev); > > nic_dev->netdev = netdev; > > diff --git a/drivers/net/ethernet/huawei/hinic/hinic_port.c b/drivers/net/ethernet/huawei/hinic/hinic_port.c > > index 28ae6f1201a8..0a39c3dffa9a 100644 > > --- a/drivers/net/ethernet/huawei/hinic/hinic_port.c > > +++ b/drivers/net/ethernet/huawei/hinic/hinic_port.c > > @@ -17,9 +17,6 @@ > > #include "hinic_port.h" > > #include "hinic_dev.h" > > -#define HINIC_MIN_MTU_SIZE 256 > > -#define HINIC_MAX_JUMBO_FRAME_SIZE 15872 > > - > > enum mac_op { > > MAC_DEL, > > MAC_SET, > > @@ -147,24 +144,12 @@ int hinic_port_get_mac(struct hinic_dev *nic_dev, u8 *addr) > > **/ > > int hinic_port_set_mtu(struct hinic_dev *nic_dev, int new_mtu) > > { > > - struct net_device *netdev = nic_dev->netdev; > > struct hinic_hwdev *hwdev = nic_dev->hwdev; > > struct hinic_port_mtu_cmd port_mtu_cmd; > > struct hinic_hwif *hwif = hwdev->hwif; > > u16 out_size = sizeof(port_mtu_cmd); > > struct pci_dev *pdev = hwif->pdev; > > - int err, max_frame; > > - > > - if (new_mtu < HINIC_MIN_MTU_SIZE) { > > - netif_err(nic_dev, drv, netdev, "mtu < MIN MTU size"); > > - return -EINVAL; > > - } > > - > > - max_frame = new_mtu + ETH_HLEN + ETH_FCS_LEN; > > - if (max_frame > HINIC_MAX_JUMBO_FRAME_SIZE) { > > - netif_err(nic_dev, drv, netdev, "mtu > MAX MTU size"); > > - return -EINVAL; > > - } > > + int err; > > port_mtu_cmd.func_idx = HINIC_HWIF_FUNC_IDX(hwif); > > port_mtu_cmd.mtu = new_mtu; > > Hi Cai: > You cannot change the maximum supported jumbo frame size. > Because as far as I know, this is not compatible with the older > firmware version. If you change the maximum MTU, the maximum length > of packets received by the port will be affected with older fw. So > donot change it. > > Zhengchao Shao