Re: [PATCH 1/5] lmb: replace lmb_reserve() and lmb_alloc_addr() API's

2025-05-02 Thread Sughosh Ganu
On Fri, 2 May 2025 at 12:21, Ilias Apalodimas wrote: > > Hi Sughosh, > > Thanks for cleaning this > > [...] > > > + * @flags: Memory region attributes to be set > > + * > > + * Allocate a region of memory where the allocation is based on the > > parameters > > + * that have been passed

Re: [PATCH 1/5] lmb: replace lmb_reserve() and lmb_alloc_addr() API's

2025-05-01 Thread Ilias Apalodimas
Hi Sughosh, Thanks for cleaning this [...] > + * @flags: Memory region attributes to be set > + * > + * Allocate a region of memory where the allocation is based on the > parameters > + * that have been passed to the function.The first parameter specifies the > + * type of allocation

[PATCH 1/5] lmb: replace lmb_reserve() and lmb_alloc_addr() API's

2025-05-01 Thread Sughosh Ganu
There currently are multiple allocation API's in the LMB module. There are a couple of API's for allocating memory(lmb_alloc() and lmb_alloc_base()), and then there are two for requesting a reservation for a particular memory region (lmb_reserve() and lmb_alloc_addr()). Introduce a single API lmb_a