From: Linus Torvalds <torvalds@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Harry Yoo <harry.yoo@oracle.com>,
David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@gentwo.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [GIT PULL] slab fix for 6.18-rc7
Date: Thu, 20 Nov 2025 13:55:51 -0800 [thread overview]
Message-ID: <CAHk-=wi-y+euEWAM9=Ns_kTXTABkwR0_MBPXf5iq5uuxfadVSQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whk_gUfFKtZrjd6TbaR0YhEmhOAs9wXFg5Je3FzQ3adAw@mail.gmail.com>
On Thu, 20 Nov 2025 at 13:37, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> HIGHMEM was a mistake forced on us by bad hardware. We should revel in
> the fact that it is not really relevant any more.
Btw. there are probably many other cases where we might just say "this
makes no sense in HIGHMEM".
But most of the time, it's not worth actively removing support for it
- it's just more work.
But when there's a case like this mempool debug thing, just say "we
don't care about this debug feature for HIGHMEM" rather than trying to
actually deal with it.
IOW, just don't write extra code for it.
Linus
next prev parent reply other threads:[~2025-11-20 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 18:45 Vlastimil Babka
2025-11-20 18:58 ` Linus Torvalds
2025-11-20 20:11 ` Matthew Wilcox
2025-11-20 21:37 ` Linus Torvalds
2025-11-20 21:55 ` Linus Torvalds [this message]
2025-11-20 19:00 ` pr-tracker-bot
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='CAHk-=wi-y+euEWAM9=Ns_kTXTABkwR0_MBPXf5iq5uuxfadVSQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=harry.yoo@oracle.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox