[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wi2TN7Zj1uBGFo8H4dhxCgp-SPdon_Wm6kC8cYO8-i9Zw@mail.gmail.com>
Date: Tue, 1 Nov 2022 10:42:11 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: x86@...nel.org, willy@...radead.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
aarcange@...hat.com, kirill.shutemov@...ux.intel.com,
jroedel@...e.de, ubizjak@...il.com
Subject: Re: [PATCH 04/13] mm: Fix pmd_read_atomic()
On Tue, Nov 1, 2022 at 5:42 AM Peter Zijlstra <peterz@...radead.org> wrote:
>
> So I've stuck the below on. There's a *TON* more to convert and I'm not
> going to be doing that just now (seems like a clever enough script
> should be able to), but this gets rid of the new one I introduced.
Thanks.
And no, I don't think the churn of converting old cases is worth it. I
just want to discourage *more* of this.
Using the same name really helps when you do a "git grep" for a
symbol, the whole '#ifndef' patterns for alternate architecture
definitions shows up really clearly.
So that - together with not having the possibility of mixing up names
- is the main reason I don't like the ARCH_HAS_XYZ pattern, and much
prefer just using the name of whichever function gets an architecture
override.
Linus
PS. I'd love to get an ack/nak on the "mm: delay rmap removal until
after TLB flush" thing.
Powered by blists - more mailing lists