From nobody Mon Nov 17 20:54:33 2025 X-Original-To: arch@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 4d9KkC6GgYz6Gwvb for ; Mon, 17 Nov 2025 20:54:43 +0000 (UTC) (envelope-from vadimnuclight@gmail.com) Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4d9KkC34lDz3LvS for ; Mon, 17 Nov 2025 20:54:43 +0000 (UTC) (envelope-from vadimnuclight@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x12b.google.com with SMTP id 2adb3069b0e04-59431f57bf6so4883855e87.3 for ; Mon, 17 Nov 2025 12:54:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1763412877; x=1764017677; darn=freebsd.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=5tIE7/JmcaQQmpQRZqPQB2QphWJvCSxMNQLLMyQHYnY=; b=CanTKlBG5kx4mHfV0LTvHPksWrXMtcJD4bbPktChwvZ4p5g7u2ourAx/T1g0NS/F+I ZbnUiCkPFh8Bz+UhR4p7buPDWCIuwG8mU5BXj9Ocdxn1T7HzMfDxMJPWga+HwTCnaTD7 0myRkZ90T1k/W2RoQ16/ZO53dH3b1ooTV6cIAFvGR6NeTQ13b6puYqcXXtG3D9W6FOtz u3qaG/ApfpLW3AgrLk6MGZpfv2gSshONOUZDADH7El1VzFynh8vDiQ8SGUXSDxJfRB7d iR6Gqszq3X1C54lpTFVQa/airZ+JUhiRYmveQvCgJJSRpLsetes4F5JMUnhB8GRIk2Au YjkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1763412877; x=1764017677; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=5tIE7/JmcaQQmpQRZqPQB2QphWJvCSxMNQLLMyQHYnY=; b=rwEQ1XfMgRUdT0nP81zHfwBt5GYBd5ST2to+BeSKaoawEtjEOIWI2j/dDi2H10Yp+h cLCfVsu0zEr2A93pAwG3NWm2ozRIU6MntfW3x1HZszpbUdg14Yu+MeRMlUkHSTkOFx0Y sXj+B+xVE0FuJQgSJKFaPf/Z72CTwvmeDV6zpkufmjIVSXkYckgmgIqiN8Ca7Az5gjr5 ZUvge9Km3kRsBaB2RlxZbpxq1fpcCm66tiwFK8zNgyx7o2k9GhsgqBsHyAwEoJABvSxm 9OApRoYWB+X1/F7l9N0NW8yZhkwvmIxPfmHyEUU0Xtdmz5YkgEH9y/MAR62oo+vFZWKK F3wA== X-Forwarded-Encrypted: i=1; AJvYcCVg19uohq4uvKMTArBv85jeC3Erw8Lju9zWXLyd8ZvONk2+whfrUoWguVGBa1MiBdKRSQfP@freebsd.org X-Gm-Message-State: AOJu0YzRMdbydK/iWRKOOLQzR944jhfOG3GbQwJNPQhelNmU1ZskLOnB 5SReTvoLvlc96aDCsJh8XTQUlVi48K176tuJHTDq26T5PkhJxjprIlUeCINjTA== X-Gm-Gg: ASbGncuKZfVOuTX4fxrn1UoIg0tnzAIw77ejVVf+XtiDqix1NFa53/iu6seaJ4sSYr5 XbAhMMyfEY8CGb9L8dZvsOJCu2y1/dpEez0VqMZ1Kvp49o0h2i5g/SmswXvPrLRBVCt7KB+lUEd ACR/mpflXhpCgLltoAadW7fH/MFxnGlIzdcgY44clyWKmX19qrlknfQx+tMks5PBDaLt3qKY9J7 knZefdsQsMXRo4EOL6Y07u5JGFZda/BrsLW3Dkb2VVTlRCr1k4yg9lqmhb+17QglqU7YnPteWLK Fwd52LYNIG5Me2IzD7ZCu5ei00WcqF0iipYsai66hsuLZOg/8doUwwxDrOEdH1NvtYutIZMr2zs 4AzDWVj8mp2r7iFPGIrQJ+eAxXnp5rsnMIaNv48USOlTaiJ4jwv+2kDLL+x62iXS6+rsvVVGlD2 1Gvwga90F/ie1L3s4BiuhK0PeRp4lbyCsR0LhqpO089l2O13tQfN/kSA== X-Google-Smtp-Source: AGHT+IGM0K0am6AJI/5Mny0//9799zYJ4o90QCzKJbqZNVEdbpuOKLoEyHwI5xcZO0v0JJCPjToBSA== X-Received: by 2002:a05:6512:3e0a:b0:590:6598:4edf with SMTP id 2adb3069b0e04-5958426b10cmr5146576e87.47.1763412876278; Mon, 17 Nov 2025 12:54:36 -0800 (PST) Received: from nuclight.lan (broadband-77-37-180-76.ip.moscow.rt.ru. [77.37.180.76]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-595803b2e26sm3441908e87.24.2025.11.17.12.54.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Nov 2025 12:54:36 -0800 (PST) Date: Mon, 17 Nov 2025 23:54:33 +0300 From: Vadim Goncharov To: Minsoo Choo Cc: Warner Losh , "freebsd-arch@freebsd.org" Subject: Re: BE (Was: What's the plan for powerpc64 in FreeBSD 16) Message-ID: <20251117235433.3c6bda40@nuclight.lan> In-Reply-To: References: <20251117215733.65553140@nuclight.lan> X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.4) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4d9KkC34lDz3LvS On Mon, 17 Nov 2025 20:37:28 +0000 Minsoo Choo wrote: > On Monday, November 17th, 2025 at 1:57 PM, Vadim Goncharov > wrote: > > > On Mon, 17 Nov 2025 18:29:20 +0000 > > Minsoo Choo minsoochoo0122@proton.me wrote: > > > > > I was thinking about this as well since the discussion on armv7. I think > > > big-endian powerpc should be removed from releases from FreeBSD 16 for > > > the following reasons. > > > > > > - Big endian usage is not used widely anymore. Even most POWER systems on > > > linux run on little-endian, and most Linux distros like RHEL only > > > provides little-endian and not big-endian. > > > - As FreeBSD is a complete operating system, if the powerpc is causing > > > issues not only in kernel but also for utilities and ports due to lack of > > > developers and hardware, there is no need to maintain them. Linux is a > > > kernel, so Linux developers can maintain kernel only for powerpc64be and > > > other developers take the responsibility of implementing libraries and > > > utilities. FreeBSD cannot take this approach, and if the cost is bigger > > > than the benefit, we should remove it. > > > - This also applies to deprecation of 32-bit platforms, but there is no > > > need to consider big endian compatibility unless we have valid reason. > > > So far, all the major platforms we support are little-endian or > > > bi-endian, and even bi-endian platforms like aarch64 and POWER mostly > > > run on little endian operating systems. Is there a new architecture or > > > even ongoing discussion of them that will be based on big endian (or > > > 32-bit) where FreeBSD can shine? If not, there is no need to consider > > > compatibility for future architectures. > > > > > > This does not mean that such will never arise in the future, especially > > given that big-endian is better; and there were such rumors/tries for > > RISC-V. > > Right, we don't know if big-endian will be trend in future. However, I'm > against preparing next big-endian architecture too proactively. As I stated > above, I don't see any big-endian architecture where FreeBSD can shine, and > this includes RISC-V big-endian. A few weeks ago, someone tried to upstream > riscvbe to Linux kernel, and Linus Torvalds was strongly against it [1], and > I think although he talked bit aggressively (as always), his claim itself > sounds reasonable. > > [1] https://www.phoronix.com/news/Torvalds-No-RISC-V-BE. Torvalds, as usual in history, just aggressively pushes his unargumented shit, e.g. remember kqueue vs epoll with nonsense arguments just to not acknowledge BSD superiority in area; this time about BE is not exception. -- WBR, @nuclight