From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id AA499A0547; Mon, 5 Dec 2022 12:15:20 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 58CD142B8B; Mon, 5 Dec 2022 12:15:20 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 0C30041144 for ; Mon, 5 Dec 2022 12:15:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1670238918; 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: in-reply-to:in-reply-to:references:references; bh=jDhys5dakbF/jHl7fLIFwgeeWS48lZssxNlq+aa2KuE=; b=LGh5p4ea6JzfCfz9FVo3vyqcQ5b4Ab73XOF+tlhTZNiOqYsVEDNNst79GiX60bV0UpH1E6 atCzkKtLzf4vFesLwD+HRA3tPjAO8jvDGcHsvJZo82u8FEL8Lm97gMUSlvvkwVFP8+ha5y oBsPUQmHy6vm3NTYQ94iB7uF54TCyI0= Received: from mail-pf1-f198.google.com (mail-pf1-f198.google.com [209.85.210.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-76-s8f1S5wnNIKKxJI5yZ8ujA-1; Mon, 05 Dec 2022 06:15:17 -0500 X-MC-Unique: s8f1S5wnNIKKxJI5yZ8ujA-1 Received: by mail-pf1-f198.google.com with SMTP id y11-20020a056a00190b00b005749340b8a8so10611097pfi.11 for ; Mon, 05 Dec 2022 03:15:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=jDhys5dakbF/jHl7fLIFwgeeWS48lZssxNlq+aa2KuE=; b=A2/iRgvfmIrTOJR0tKVrSADeUUFycD59/krYRJxCBq5jOwuuv9EsCrJVt86acBSX6j dfkcnfkGYoOGzxAKWjyRoU/ECD66qBhl4QTsKet5zV1cpV/Y5xRS5IDkJcmuzINAtNZ3 fDB2MTh5UnMWKItBKQnZxbHvN3kBp7W2uXfEOamXJFWrv7EzKYsELyU8EFarUOLMcBpD Ktg85cYGiNhEnidab4N7VuNPCrRow8GgAd/Adx4nGgE0PFewGVb6c3qJWcGOUst058+1 oXQYe+hue0XbRr4KRZRJqbfIUjRXbcM5t8sN8xMIw2t7+7PhPdeJO2UWBb8tMVS1Cww+ 2kUg== X-Gm-Message-State: ANoB5pkVi7pdZUNM5GvrdLtUcOD+ct3V/awXGCZIGLYVKCwj9gbQd3Bv pPV3oJ+wJE+sEPNn4U0LC4ebKCdwZY6PJQAsQqMX33EJuchJxl1NaZ9ecjYXWuwtfQxQ2oOXdQJ TknMG4wgibLcgewkN0AU= X-Received: by 2002:a63:2163:0:b0:474:d6fa:f574 with SMTP id s35-20020a632163000000b00474d6faf574mr59541660pgm.190.1670238916417; Mon, 05 Dec 2022 03:15:16 -0800 (PST) X-Google-Smtp-Source: AA0mqf5VGwXnpkn/26QPboRXmOfiMW4IpfhIZL3sGMao05YHZtKUPTjjk7cKb9mQGj0UeMOBPsBulG0km4bK0NVhPLw= X-Received: by 2002:a63:2163:0:b0:474:d6fa:f574 with SMTP id s35-20020a632163000000b00474d6faf574mr59541628pgm.190.1670238916093; Mon, 05 Dec 2022 03:15:16 -0800 (PST) MIME-Version: 1.0 References: <20221110034524.467431-1-jie1x.wang@intel.com> In-Reply-To: From: David Marchand Date: Mon, 5 Dec 2022 12:15:04 +0100 Message-ID: Subject: Re: [PATCH] net/i40e: fix X722 NIC receives jumbo frame packets To: Kevin Traynor , "Zhang, Qi Z" Cc: "stable@dpdk.org" , "Yuan, DukaiX" , "Wang, Jie1X" , "dev@dpdk.org" , "Yang, SteveX" , "Yang, Qiming" , "Xing, Beilei" , "Zhang, Yuying" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi Kevin, Qi, On Thu, Nov 10, 2022 at 10:48 AM Zhang, Qi Z wrote: > > > Subject: [PATCH] net/i40e: fix X722 NIC receives jumbo frame packets > > > > > > For NIC I40E_10G-10G_BASE_T_X722, when the port is configured with > > > link speed, it cannot receive jumbo frame packets. > > > > > > Because it set maximum frame size failed when starts the port that the > > > port link status is still down. > > > > > > This patch fix the error that starts the port will force set maximum frame > > size. > > > > > > Fixes: 2184f7cdeeaa ("net/i40e: fix max frame size config at port > > > level") > > > Cc: stable@dpdk.org > > > > > > Signed-off-by: Jie Wang It seems this fix has been missed in 21.11 (for the reason we discussed with Kevin offlist). Our QE reported that reception of jumbo frames seems broken in the 21.11 branch. I can reproduce with a X710 nic: v21.11.0 is fine, but v21.11.1 and v21.11.2 show the following error log. Dec 05 05:41:37 xxx ovs-vswitchd[53585]: ovs|00183|dpdk|ERR|i40e_set_mac_max_frame(): Set max frame size at port level not applicable on link down The log goes away with backporting this current patch. Can this be added to 21.11 queue, and have Intel validate this issue? Thanks! -- David Marchand