Re: [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v3)

On 16/02/2022 10:36, Christian König wrote: Am 15.02.22 um 23:23 schrieb Vivek Kasireddy: This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficiently traversing the rbtree associated with the given

Re: [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v3)

Am 15.02.22 um 23:23 schrieb Vivek Kasireddy: This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficiently traversing the rbtree associated with the given allocator. It replaces the for loop in

[PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v3)

This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficiently traversing the rbtree associated with the given allocator. It replaces the for loop in drm_mm_insert_node_in_range() and can also be used by drm

[PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v3)

This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficiently traversing the rbtree associated with the given allocator. It replaces the for loop in drm_mm_insert_node_in_range() and can also be used by drm

Re: [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v2)

On 04/02/2022 01:19, Vivek Kasireddy wrote: This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficiently traversing the rbtree associated with the given allocator. It replaces the for loop in

[PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v2)

This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficiently traversing the rbtree associated with the given allocator. It replaces the for loop in drm_mm_insert_node_in_range() and can also be used by drm

RE: [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation

Hi Tvrtko, > -Original Message- > From: Tvrtko Ursulin > Sent: Wednesday, February 02, 2022 5:04 AM > To: Kasireddy, Vivek ; > dri-devel@lists.freedesktop.org > Subject: Re: [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes > for an > allocation > > > On 02/02/2022

Re: [PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation

On 02/02/2022 01:13, Vivek Kasireddy wrote: This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficently traversing the rbtree associated with the given allocator. It replaces the for loop in

[PATCH 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation

This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficently traversing the rbtree associated with the given allocator. It replaces the for loop in drm_mm_insert_node_in_range() and can also be used by drm