[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210916093721.4508a5b3@gandalf.local.home>
Date: Thu, 16 Sep 2021 09:37:21 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Peter Zijlstra <peterz@...radead.org>,
Gabriel Krisman Bertazi <krisman@...labora.com>,
André Almeida <andrealmeid@...labora.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Darren Hart <dvhart@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Collabora kernel ML <kernel@...labora.com>,
Linux API <linux-api@...r.kernel.org>,
GNU C Library <libc-alpha@...rceware.org>,
Michael Kerrisk <mtk.manpages@...il.com>,
Davidlohr Bueso <dave@...olabs.net>
Subject: Re: [PATCH v3 2/6] futex2: Implement vectorized wait
On Thu, 16 Sep 2021 13:50:14 +0200
Arnd Bergmann <arnd@...db.de> wrote:
> Similar logic applies to cloud instances or containers. Running a 32-bit
> Alpine Linux in a container means you can often go to a lower memory
> instance on the host compared to a full 64-bit distro.
I also found that running a 32 bit version of Chrome or FireFox keeps them
from taking up all the memory in your system ;-) The most they can use is
4 gigs.
-- Steve
Powered by blists - more mailing lists