The LMB memory allocation module currently supports two classes of API’s. The first set is the allocation API’s, which allocate free/available memory. The second set of API’s are for ‘reserving’ memory. Which is a behavior which is specific to U-Boot. These reservations might include re-requesting already reserved/in-use memory, when the API is called with a certain flag.
Instead of these two classes of API’s, we can have a single API which can handle both sets of requests, allocations as well as reservations. Work on optimizing the current LMB code so as to have a single API.
High
The LMB memory allocation module currently supports two classes of API’s. The first set is the allocation API’s, which allocate free/available memory. The second set of API’s are for ‘reserving’ memory. Which is a behavior which is specific to U-Boot. These reservations might include re-requesting already reserved/in-use memory, when the API is called with a certain flag.
Instead of these two classes of API’s, we can have a single API which can handle both sets of requests, allocations as well as reservations. Work on optimizing the current LMB code so as to have a single API.