From nobody Mon Nov 13 19:27:05 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4STfZZ6kTgz50Rch for ; Mon, 13 Nov 2023 19:27:18 +0000 (UTC) (envelope-from soren.schmidt@gmail.com) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4STfZZ51xhz4f0B for ; Mon, 13 Nov 2023 19:27:18 +0000 (UTC) (envelope-from soren.schmidt@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x334.google.com with SMTP id 5b1f17b1804b1-4083f613275so39921765e9.2 for ; Mon, 13 Nov 2023 11:27:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699903636; x=1700508436; darn=freebsd.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=d0xxHUOev9FQ9zumC2yP1Wqg6NUGLMl+f9QYnGwkw3I=; b=N4iPYFbM1fkO/sZIXgP4Nb0YWIBpBLfmQBRODQCPKY4xvsMpMj1NCCeKrAxJC9bTbC MG/kjSGWJMMdsxnX0wnyWpavL4qKrFHNaPg44vOEF4B62vxh9gRgtI0ZSAIyJ9G3oy/I K6CBVUQP1RN1yPq/WW7mj13NSYHddA8y4HQLcXnDh6WZrMes/lyr0ntcMx4Mr8lrgZGp N26+zKkM0aI1QpSL/5PcJM2FJKmsrPY96B1lahwZz0D6oXYPXhVYWBZAcL06gDbT+Pki bdYme/w5jtBoYxY3EWlqWOjngJvpYxyJ+AxM17kTwa7angG+14oxqMLSXH+Qis9Gvigg U2oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699903636; x=1700508436; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=d0xxHUOev9FQ9zumC2yP1Wqg6NUGLMl+f9QYnGwkw3I=; b=MHI0xXwyZpM6XtQ3P5FNrsWRH1H1CO+CfwPdE7g6EPZSDyT+GOy1d1lqeQtRVr4QdK Y/lKfqvvMllPPQf3oHzc603F5RBNWRWTXF4W74kuRbC1EVJXUk4K2JqC+clgNCPr9ayL F0RY4KUNfDkyMllcQBAEJeYmC4zVHVTuEV99Yc9Tk/4IKuDJwLD5pdd1DToV7snKV6AQ wj9fz9VbNd+F3PUylF+J1UAdE3uLt/hAC6oIdvt6ClsVtY21SBp70vjMAqAzHgUghaHq 6Viz6kphB6qT1uB9vw4daDrvkgJLxci2ifhGOKf2KjtftGr9fL83mQ+hK20YVpuNkLNE tshQ== X-Gm-Message-State: AOJu0YzNu0sYl/O8Y13sgbRwkiPNzqJKQk5oJtZrO4oc2bN94exz/qPO PjHPXhEy4M+Dp4LCvDF+UlAFtaQbERQ= X-Google-Smtp-Source: AGHT+IGh51UkPXUzmleykNZvsDb90kzJ+hAQeJXpnq4faT/dPlReXhpWKv2hfy4Wl2IneD3qxkxXSQ== X-Received: by 2002:a05:600c:1991:b0:405:3e9a:f1e3 with SMTP id t17-20020a05600c199100b004053e9af1e3mr6206821wmq.11.1699903635926; Mon, 13 Nov 2023 11:27:15 -0800 (PST) Received: from smtpclient.apple ([85.27.186.9]) by smtp.gmail.com with ESMTPSA id dl3-20020a0560000b8300b0032f79e55eb8sm6036262wrb.16.2023.11.13.11.27.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Nov 2023 11:27:15 -0800 (PST) Content-Type: text/plain; charset=utf-8 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\)) Subject: Re: eqos(4) throughput From: =?utf-8?Q?S=C3=B8ren_Schmidt?= In-Reply-To: <0FA5C2FB-B336-4DFA-AD32-05C414DDB6F7@edc.ro> Date: Mon, 13 Nov 2023 20:27:05 +0100 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <5C1C084D-00A2-4FF3-9A14-34017DC9A4EE@gmail.com> References: <0FA5C2FB-B336-4DFA-AD32-05C414DDB6F7@edc.ro> To: titus X-Mailer: Apple Mail (2.3731.700.6) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Queue-Id: 4STfZZ51xhz4f0B On 13 Nov 2023, at 16.40, titus wrote: > i have this problem with eqos(4) on a rk3566 board (orangepi 3b) > when there is enough RX traffic the TX sinks packets (not all the = packets are transmitted) > this causes a max tcp uplink throughput of about 300mb/s > testing udp tx only will get to 900mbs+ > testing with iperf -c -u -b 700m -d > will show 25-30% of the tx packets lost > the 25-30 percent can be decreased slightly if i fiddle with dtb = ethernet tx_delay but 19% is the best i could get >=20 > can somebody running 14+ on an rk356x board test this > on box1=20 > (server) iperf -s -u > on box2 rk356x (client) > iperf -c -b 700m -u -d > and check the packets lost by client send stream ? I can confirm this on the boards I have access to here, quartz64, = Nanopi5, firefly station m2/p2. around 400mbit bandwitdth and 16% loss, thats running CPU at 2.2Ghz. If I set 400Mhz CPU clock I get 375mbit and 0.6% loss, thats odd at = least. Anyhow the eqos driver is far from perfect, its single queue only etc, = so there is possibly much to be gained. -- S=C3=B8ren Schmidt sos@deepcore.dk / sos@freebsd.org "So much code to hack, so little time"=