All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tomas Glozar <tglozar@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	"H . Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
	Thomas Gleixner <tglx@kernel.org>
Subject: Re: [PATCH] x86: Start removing X86_X32_ABI
Date: Mon, 1 Jun 2026 23:26:41 +0200	[thread overview]
Message-ID: <20260601212641.3OMNe1Gi@linutronix.de> (raw)
In-Reply-To: <20260528070548.2967334-1-tglozar@kernel.org>

On 2026-05-28 09:05:48 [+0200], Tomas Glozar wrote:
> FWIW, T2 Linux [1] also has an option to build x32, and there have been such
> builds last year [2]. Since this year, it switched to building KDE Plasma
> desktop ISOs, where x32 makes less sense, though, as modern desktop is rather
> RAM-hungry.

I wasn't aware of this. If an application, such as chromium, is memory
hungry the x32 doesn't help much to contain it. Your pointer are
smaller, granted, but the overall memory consumption is still
significant. Running x32 means also that a single application is not
able to use more than 4GiB or memory.

> [1] https://t2linux.com
> [2] https://dl.t2sde.org/binary/2025/t2-25.10-x32-base-wayland-glibc-gcc-nocona.iso
> 
> Also at least 6 years ago, x32 was reported there to increase performance by
> some 5-8% [3] likely thanks to smaller pointers allowing better cache
> utilization. That is not insignificant, and not all tasks require gigabytes of
> RAM (e.g. compression and encryption, as shown in the link).

Arnd told me quite some time ago that cross compiling (or compiling in
general) has better performance on x32 than x86-64. This was the only
case afaik. 

> [3] https://www.youtube.com/live/Mw-ravkg67k?si=HS7ZHZyg_FKXPZUz&t=387 (yeah
> YouTube video not the best source...)

So from that linked video, there few cases where x32 builds quicker. But
then at 9.51 there is runtime x64-O2 is leading. The video is titled
5%-8% but I don't see where this is from.

> Tomas

Sebastian

  reply	other threads:[~2026-06-01 21:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23  9:37 [PATCH] x86: Start removing X86_X32_ABI Sebastian Andrzej Siewior
2026-05-23 21:43 ` H. Peter Anvin
2026-05-26 10:40   ` Sebastian Andrzej Siewior
2026-05-26 15:53     ` H. Peter Anvin
2026-05-26 15:54     ` H. Peter Anvin
2026-05-26 20:43       ` Sebastian Andrzej Siewior
2026-05-31 21:46         ` Arnd Bergmann
2026-06-01 21:44           ` Sebastian Andrzej Siewior
2026-06-01 22:45             ` Arnd Bergmann
2026-05-27 12:02       ` David Laight
2026-06-01 21:29         ` H. Peter Anvin
2026-06-04 20:27   ` Thomas Gleixner
2026-05-27 13:10 ` Sam James
2026-05-27 13:41 ` Neal Gompa
2026-05-27 15:57 ` John Paul Adrian Glaubitz
2026-06-01 21:12   ` Sebastian Andrzej Siewior
2026-06-01 21:14     ` H. Peter Anvin
2026-05-28  7:05 ` Tomas Glozar
2026-06-01 21:26   ` Sebastian Andrzej Siewior [this message]
2026-05-31 22:05 ` Arnd Bergmann
2026-06-02 16:02   ` Maciej W. Rozycki
2026-06-02 16:36     ` Arnd Bergmann
2026-06-05  3:35       ` H. Peter Anvin
2026-06-02  9:48 ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260601212641.3OMNe1Gi@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglozar@kernel.org \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.