Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp37676963rwd; Tue, 11 Jul 2023 18:35:16 -0700 (PDT) X-Google-Smtp-Source: APBJJlGpRyCrH/RpM4xMLG0RDFm76oXjvPMfe04hKlPxRRKLf/KKZ3KJlrKiR++b3nQBu2iLYm6d X-Received: by 2002:a17:906:1c17:b0:991:b554:e64b with SMTP id k23-20020a1709061c1700b00991b554e64bmr16266996ejg.54.1689125716613; Tue, 11 Jul 2023 18:35:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689125716; cv=none; d=google.com; s=arc-20160816; b=h+W4X1Q8pJ3MykJGqmcbiK/6NRgm7AhRQvJD2h2ZlbEu1T27LRYFikxTkCrHlf94SL OKjtGjk8M5tbXcCHtlfxR254yL8zPzNlVt5B+oVbXpJRuhA8vUHOGShpgE1jhJrEHul6 u9AKjIBdv3KYPAkzRVpAmiqBHfFuDAP6LMS0EBOe1PQUvO0lHRE4kAgYwdodmLphnLR3 8JUYxJUoRRfdtKwt2Wof/XGxEdqWp+qFx/AJWW+ljVLo/dWwlVBQz9q4DZW9s3vQ7NvW 0i0bbS13tjOuA2npFDseDSCMyr8F0K/H/VZC2YFnT6HmOP01zJUfQz1o1IkEQADGsgdC JhPA== 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-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=dVMRKCtThpA0k7vZMvJIKRYdajbcjdgx3zkYzglFpvU=; fh=Xobd5Riai1OA982CJPuVqK/VkEWdlP4OnOTG4VFHBmI=; b=vWwkzMYW0mHXJ/FqNjppHHifqxtrmaV951XEvvFoZrwqIu+3UKPNFf6KyKxAt6WM4q zrUBde0cKrduSenkBhZIWvFPBBllFSSOdvccETa6NI8hyBgdUvC0WW4e7Hy1ub624Hy1 CPw7BVSaMGCB3ZL+xKEPhMK5Wyeus2GmnyDDj3FLuoNCQSzEhzgcezA6XHIrBnkyfclf kTOr07kewNn6oe7JsPNzzTkaE8k+sRrjxTHqkcLUo9zT+eGBpujKSiF9W+0cfZu1iew1 93xvFBuLFUvRXLpVm4NlxoUJ5HOpHhFYi78FgSL1jKundu14LoHvp8xa31WcJUtZPXOZ Y7gA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=AGieYMQV; 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=lunn.ch Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q6-20020a1709064cc600b0098889bf7f86si3556830ejt.315.2023.07.11.18.34.52; Tue, 11 Jul 2023 18:35:16 -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=@lunn.ch header.s=20171124 header.b=AGieYMQV; 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=lunn.ch Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229524AbjGLBQn (ORCPT + 99 others); Tue, 11 Jul 2023 21:16:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47546 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230327AbjGLBQl (ORCPT ); Tue, 11 Jul 2023 21:16:41 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ED1981726; Tue, 11 Jul 2023 18:16:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=dVMRKCtThpA0k7vZMvJIKRYdajbcjdgx3zkYzglFpvU=; b=AGieYMQVYFIP8kjVmm6NG4qKnJ mjj6Q9142L9yaOxC7IH158DUfTGzsqxXCtxHpgaU7tCgpJKxfq4giT0KqlzQgrSIvA+naYP1nsNW1 vzEPPfo1u3rAbW0iuKuG+u0SnjWEvX7CD8/cQKZeSmPVPpEoL54n3yQiUfp3cpNiA9Ps=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1qJOSs-0015Xo-Hq; Wed, 12 Jul 2023 03:16:22 +0200 Date: Wed, 12 Jul 2023 03:16:22 +0200 From: Andrew Lunn To: Wei Fang Cc: "davem@davemloft.net" , "edumazet@google.com" , "kuba@kernel.org" , "pabeni@redhat.com" , "ast@kernel.org" , "daniel@iogearbox.net" , "hawk@kernel.org" , "john.fastabend@gmail.com" , Shenwei Wang , Clark Wang , "netdev@vger.kernel.org" , dl-linux-imx , "linux-kernel@vger.kernel.org" , "bpf@vger.kernel.org" Subject: Re: [PATCH net 3/3] net: fec: increase the size of tx ring and update thresholds of tx ring Message-ID: References: <20230704082916.2135501-1-wei.fang@nxp.com> <20230704082916.2135501-4-wei.fang@nxp.com> <0443a057-767f-4f9c-afd2-37d26b606d74@lunn.ch> <757f7803-72b6-4649-bfff-e4559d269880@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED, SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 > Sorry, the Vybrid platform is not currently maintained by us, and Vybrid is also not > included in our usual Yocto SDK RC version. Your Yocto SDK version does not matter. We are talking about mainline here... You are maintaining the mainline driver, and submitting patches to extend the mainline driver. > Even I find a Vybrid board, I think it > probably cann't run with the latest kernel image, because the latest kernel image > does not match with the old Yocto SDK, and new Yocto SDK does not support Vybrid > platform. I also asked my colleague in test team who is in charge of ethernet testing, > she hadn't even heard of Vybrid platform. Well 6.5-rc1 does run on Vybrid, i have a number of boards with it. You will also find that many inflight entertainment systems have a box under each row of seats in a aeroplane with a Vybrid controlling a Marvell switch. Take a look at arch/arm/boot/dts/vf610-zii-* You will also find a number of DTS files for imx5i, imx6, imx7 used for ZII products which are back of the seat displays, and make heavy use of networking with the FEC. So i have in interest in the FEC for all these platforms. > > And a bigger burst means more latency. Read about Buffer bloat. > > > Perhaps, but not necessarily. For example, in some cases that some burst packets > maybe stay in Qdisc instead of hardware queue if ring size is small. Which is what you want, so high priority packets can jump to the head of the queue. > > While you have iperf running saturating the link, try a ping as well. How does > > ping latency change with more TX buffers? > > > Per your suggestions, I tested on i.MX8ULP, i.MX8MM and i.MX93 platforms. The > results do not appear to be very different. Thanks for the benchmark numbers. They look O.K. Andrew