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 27289A0547 for ; Mon, 5 Dec 2022 12:15:23 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 163D242D20; Mon, 5 Dec 2022 12:15:23 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 1F33242D1F for ; Mon, 5 Dec 2022 12:15:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1670238920; 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=X8zXX2n3PcOgmbI4zaD6JUadO/Pd3U6h3sh9Q5kG0+7mvILQhwaaEemBSrXL8bppQAWqj8 SDtR+VYArvi6+EW7h6to4iIxApoktSzrpbAf9zWx2ee93/JAOW56cPxBPiTTyUWK7Vo9T7 qB90CiyJlz+Y2XLm9YpeVDLuQK2Ol9Y= Received: from mail-pg1-f198.google.com (mail-pg1-f198.google.com [209.85.215.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-547-arpe0vvyNLmti6odKSDRyA-1; Mon, 05 Dec 2022 06:15:17 -0500 X-MC-Unique: arpe0vvyNLmti6odKSDRyA-1 Received: by mail-pg1-f198.google.com with SMTP id 69-20020a630148000000b00478118684c4so9886776pgb.20 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=2vxHZIr1JnJWLjv2NH2buz2iJKeDxVGrOB9Iiki8+iqwZHLAPNzZgjO97XFevJeeFd EjWtXsL5J/9mpCjgwaLTgA2bbOVmEVrVkUN1NV25Jfh4V2V8B0+k/6RMep4kN9kV+ylM DqVWYBVdkTK9WD6r9H81u9KrkAi8gxPfbChJ6GkTd1VpMlXXVLz+7xkl6sBaZDfCnEDP JcmFP6lm5QJVJc1hHh5rUn7kivlTwcSSgeExEPyFNY7GyEHcP5xQqAqpH80hTX7QMTJT C4RHjyxHWFU6y5EKoByZz7QfdyU15soqvNCxwF09HmueK1VM9V5dPgkIJeli75gtR/P3 nBbQ== X-Gm-Message-State: ANoB5pl60fKDausU52aGnwwTUQiItaPj0/rXz0DJMJhh+z5H5mLTDdJM OAuB32K6jqJZmy/lvJd7AfD10Zgo1CrIVzJr09BhFsQSfjQeoOSjPLqfV0KBV4CDrJ8vOQ6ZNYn 7mXifTPnzCDK0DQFEGU6Vc0I= X-Received: by 2002:a63:2163:0:b0:474:d6fa:f574 with SMTP id s35-20020a632163000000b00474d6faf574mr59541654pgm.190.1670238916414; 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: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-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