From nobody Wed Jun 23 11:47:41 2021 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 137F111DBF7A for ; Wed, 23 Jun 2021 11:49:05 +0000 (UTC) (envelope-from denis@ovsienko.info) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4G91kl5tcxz4Y5D for ; Wed, 23 Jun 2021 11:49:03 +0000 (UTC) (envelope-from denis@ovsienko.info) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ovsienko.info; s=selector2; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:To:From:Date; bh=s/nJYEJNBZndHBJoDAunSnAkSufTt0k6B3m9AtpoUdg=; b=keugmNLQ9H0tl5UsYesBiPJscl pRKL+lTJG1j5wbPTIC+iQ65Sc341AEh1Xk5PfA95t/3EAuZeGre9oipXxWQ2N5DGk3MxgtYd5f287 DWUR1c+Q8hP4wqxHYAMQWHi0HZ7buQbVwvos9jvUM8IfjibG+UuxnvSIoHhAenIA7XEfsoYAhUHW+ zmTrqndmKIhHhka6VAOdOMs/VUZG+CtcQYQUpT+shcBp1GwiibMtW2gDAK00yRMthxaudiuSWpTSp TZlmOqtu/ygG3/+6PK559dF1D/9jkhayDL1kRtL06QjeCRd6mq4g8VQz1r8MLJo0OuL0Cf2QN8OPD 9gf2EHhw==; Received: from [10.9.9.72] (helo=submission01.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1lw1NM-0001GQ-QO for freebsd-arm@freebsd.org; Wed, 23 Jun 2021 13:49:00 +0200 Received: by submission01.runbox with esmtpsa [Authenticated ID (984599)] (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) id 1lw1NC-0000SK-Kb for freebsd-arm@freebsd.org; Wed, 23 Jun 2021 13:48:50 +0200 Date: Wed, 23 Jun 2021 12:47:41 +0100 From: Denis Ovsienko To: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi 3B+ and pitiful network speeds Message-ID: <20210623124741.3b8cd018@basepc> In-Reply-To: <7f85f397-e656-4d05-b044-c079bc60d5e0@gmail.com> References: <20210620144513.1f91a68f@basepc> <169baf0b-3f3c-f1dc-4a6f-b8a0ef863f51@denninger.net> <20210620154105.0c83bbcc@basepc> <20210620222922.51da1818@basepc> <3fa3f2a6-8560-f413-b2eb-5c172ce025eb@gmail.com> <6B4F2FB6-ABA1-4CFA-BE2A-6A466C30FF02@yahoo.com> <20210621111301.75fa1c7a@basepc> <20210622133729.47b26900@basepc> <7f85f397-e656-4d05-b044-c079bc60d5e0@gmail.com> 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4G91kl5tcxz4Y5D X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ovsienko.info header.s=selector2 header.b=keugmNLQ; dmarc=none; spf=pass (mx1.freebsd.org: domain of denis@ovsienko.info designates 91.220.196.211 as permitted sender) smtp.mailfrom=denis@ovsienko.info X-Spamd-Result: default: False [-3.10 / 15.00]; MID_RHS_NOT_FQDN(0.50)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[91.220.196.211:from]; R_DKIM_ALLOW(-0.20)[ovsienko.info:s=selector2]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[91.220.196.211:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:91.220.196.211]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[ovsienko.info]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[91.220.196.211:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[ovsienko.info:+]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:50304, ipnet:91.220.196.0/24, country:NO]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm]; RCVD_IN_DNSWL_LOW(-0.10)[91.220.196.211:from] X-ThisMailContainsUnwantedMimeParts: N On Wed, 23 Jun 2021 12:30:29 +1000 MJ wrote: > I will likely abandon using FreeBSD, but I should probably raise a > bug report for this? I am not sure of the process for this or whether > it's even wanted. That is, does FreeBSD care enough about little > appliances like the Raspberry Pis to spend time fixing an obviously > broken network driver/stack? It seems to me that overall support is likely to improve in some future. Little boards are good vehicles for ramping newcomers up into the ARM space, so they do receive developer attention. That said, there's a lot of hard work involved in getting an operating system to support a particular board fully, and in some parts of the world some boards are more available than others. RPI is the type most available to me, and it is very helpful that FreeBSD provides a ready to run RPI image for download, and treats ARM as a Tier 1 architecture. Regarding your best next steps, it might help to consider two aspects of "works": functional-wise and performance-wise. Clearly, in your case there is a performance issue, and the best you can do is raise a detailed bug report. Functional-wise the fact is, some hardware features (GPIO, audio, accelerated video, I2C, WiFi, Bluetooth, etc) are not supported well or at all by particular releases of particular BSD systems on particular boards (cannot remember specifics, and it is changing all the time). So if your use case involves anything beyond USB, Ethernet (and even SD card, as it was with OpenBSD until recently!), you would have to double-check before switching to another board or another OS. With that in mind, if your project's functional requirements allow to switch to RPI4B, it might be another good thing to do whilst your RPI3B+ bug report is waiting to be resolved. There's plenty of churn in RPI4B code and it looks unlikely to fully settle anytime soon (FreeBSD is not unique in this regard), but Ethernet works OK. I have just done a quick one-way TCP throughput tests on FreeBSD/RPI4B and it resulted in 87MB/s in either direction. That's an order of magnitude more than what you are observing with RPI3B+. Once again, an even simpler way out of the performance issue might be through a USB Ethernet interface that happens to "just work", whatever the underlying reasons are. -- Denis Ovsienko