[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whYnBZzMkOOjHjhxCUmAcYVU007qhAsxDcJQc1PvEs8YA@mail.gmail.com>
Date: Fri, 26 Jul 2024 14:38:31 -0700
From: Linus Torvalds <torvalds@...uxfoundation.org>
To: David Laight <David.Laight@...lab.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>, Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Dan Carpenter <dan.carpenter@...aro.org>, Arnd Bergmann <arnd@...nel.org>,
"Jason@...c4.com" <Jason@...c4.com>, "pedro.falcato@...il.com" <pedro.falcato@...il.com>,
Mateusz Guzik <mjguzik@...il.com>, "linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [PATCH 0/7] minmax: reduce compilation time
On Fri, 26 Jul 2024 at 14:33, David Laight <David.Laight@...lab.com> wrote:
>
> I suspect just reordering to:
> extra_pages = min3(extra_pages, max_pages - max_pfn,
> EXTRA_MEM_RATIO * min(max_pfn, PFN_DOWN(MAXMEM)));
> will have a similar effect.
That's disgusting.
No, we're not adding random "the ordering of min3() matters subtly for
expansion size" crap.
We're simplifying the sub-expressions, and fixing the problem that way.
Linus
Powered by blists - more mailing lists