Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: Is there a different memory allocation path other than the buddy
 allocator?
To:     Shivank Garg <shivankgarg98@gmail.com>,
        linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        akpm@linux-foundation.org, gregkh@linuxfoundation.org,
        sergey.senozhatsky@gmail.com, pmladek@suse.com
References: <CAOVCmzEAMz4NGF3gi4O_tNUQfm2+-8AkGiOn0gPN+p3GHctkKA@mail.gmail.com>
From:   David Hildenbrand <david@redhat.com>
Organization: Red Hat
Message-ID: <88d5164f-0261-469c-5549-4d97a7936775@redhat.com>
Date:   Wed, 28 Apr 2021 16:44:36 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <CAOVCmzEAMz4NGF3gi4O_tNUQfm2+-8AkGiOn0gPN+p3GHctkKA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 28.04.21 09:37, Shivank Garg wrote:
> Hi Everyone!
> 
> I'm understanding memory allocation in Linux and doing some changes in
> buddy allocator (__alloc_pages_nodemask) for my experiments. I create
> a new flag in `struct page->flags` (by adding a new flag in `enum
> pageflags` in `page-flags.h`. I set this bit permanently in
> __alloc_pages_nodemask (to not to be cleared once set and survive all
> further allocation and freeing). But I'm not able to see expected
> behavior.
> 
> I'm guessing this is because Linux is also using some different path
> to allocate memory (probably during boot). Is my hypothesis correct?
> 
> Is there any different memory allocation path other than buddy
> allocator? Where can I find it?

memblock is the early memory allocator during boot, before the buddy is 
up and running. The range allocator (e.g., alloc_contig_range()) is some 
kind of mechanism that builds up on top of the buddy. Other allcoators 
(hugetlb, slab, ...) might cache some pages, but effectively get 
"physical memory" either via memblock or the buddy.

CMA is another special-purpose allocator which reserves physical memory 
areas via memblock and then uses the range allocator to actually 
allocate memory inside these reserved regions at runtime.

-- 
Thanks,

David / dhildenb