Re: [PATCH 3/6] mm: always inline __mk_vma_flags() and invoked functions
Andrew Morton <[email protected]> Wed, 25 Mar 2026 09:09:49 -0700
| Newsgroups | dev.linux.lists.ntfs3,dev.linux.lists.nvdimm,org.kernel.vger.linux-cxl,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel,org.kvack.linux-mm,org.ozlabs.lists.linux-erofs |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 25 Mar 2026 14:58:14 +0000 "Lorenzo Stoakes (Oracle)" <[email protected]> wrote: > On Wed, Mar 25, 2026 at 02:54:50PM +0000, Pedro Falcato wrote: > > On Thu, Mar 05, 2026 at 10:50:16AM +0000, Lorenzo Stoakes (Oracle) wrote: > > > Be explicit about __mk_vma_flags() (which is used by the mk_vma_flags() > > > macro) always being inline, as we rely on the compiler converting this > > > function into meaningful. > > meaningful what? > > 'into the equivalent compile-time constant code' probably fine. > > Andrew - could you update that if there's time? np : Be explicit about __mk_vma_flags() (which is used by the mk_vma_flags() : macro) always being inline, as we rely on the compiler converting this : function into the equivalent compile-time constant code. what does "compile-time constant code" actually mean? That constants within the code are evaluated at compile-time?