From: Nirmoy <nirmodas@amd.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
chris@chris-wilson.co.uk, intel-gfx@lists.freedesktop.org,
nirmoy.das@amd.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/mm: optimize find_hole() as well
Date: Mon, 15 Jun 2020 18:54:47 +0200 [thread overview]
Message-ID: <060aa4b7-54ca-1621-4bf2-b018f7da0121@amd.com> (raw)
In-Reply-To: <20200615145415.1775-2-christian.koenig@amd.com>
Acked-by: Nirmoy Das <nirmoy.das@amd.com>
On 6/15/20 4:54 PM, Christian König wrote:
> Abort early if there isn't enough space to allocate from a subtree.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/drm_mm.c | 11 +++++++----
> drivers/gpu/drm/selftests/test-drm_mm.c | 11 -----------
> 2 files changed, 7 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c
> index 425fcd3590e8..177a5df0fe95 100644
> --- a/drivers/gpu/drm/drm_mm.c
> +++ b/drivers/gpu/drm/drm_mm.c
> @@ -325,7 +325,7 @@ static struct drm_mm_node *best_hole(struct drm_mm *mm, u64 size)
> return best;
> }
>
> -static struct drm_mm_node *find_hole(struct drm_mm *mm, u64 addr)
> +static struct drm_mm_node *find_hole_addr(struct drm_mm *mm, u64 addr, u64 size)
> {
> struct rb_node *rb = mm->holes_addr.rb_node;
> struct drm_mm_node *node = NULL;
> @@ -333,6 +333,9 @@ static struct drm_mm_node *find_hole(struct drm_mm *mm, u64 addr)
> while (rb) {
> u64 hole_start;
>
> + if (rb_hole_addr_to_node(rb)->subtree_max_hole < size)
> + break;
> +
> node = rb_hole_addr_to_node(rb);
> hole_start = __drm_mm_hole_node_start(node);
>
> @@ -358,10 +361,10 @@ first_hole(struct drm_mm *mm,
> return best_hole(mm, size);
>
> case DRM_MM_INSERT_LOW:
> - return find_hole(mm, start);
> + return find_hole_addr(mm, start, size);
>
> case DRM_MM_INSERT_HIGH:
> - return find_hole(mm, end);
> + return find_hole_addr(mm, end, size);
>
> case DRM_MM_INSERT_EVICT:
> return list_first_entry_or_null(&mm->hole_stack,
> @@ -497,7 +500,7 @@ int drm_mm_reserve_node(struct drm_mm *mm, struct drm_mm_node *node)
> return -ENOSPC;
>
> /* Find the relevant hole to add our node to */
> - hole = find_hole(mm, node->start);
> + hole = find_hole_addr(mm, node->start, 0);
> if (!hole)
> return -ENOSPC;
>
> diff --git a/drivers/gpu/drm/selftests/test-drm_mm.c b/drivers/gpu/drm/selftests/test-drm_mm.c
> index ca5f35def905..b879aedfc00d 100644
> --- a/drivers/gpu/drm/selftests/test-drm_mm.c
> +++ b/drivers/gpu/drm/selftests/test-drm_mm.c
> @@ -1981,16 +1981,6 @@ static int __igt_once(unsigned int mode)
> }
>
> memset(&node, 0, sizeof(node));
> - err = drm_mm_insert_node_generic(&mm, &node,
> - 2, 0, 0,
> - mode | DRM_MM_INSERT_ONCE);
> - if (!err) {
> - pr_err("Unexpectedly inserted the node into the wrong hole: node.start=%llx\n",
> - node.start);
> - err = -EINVAL;
> - goto err_node;
> - }
> -
> err = drm_mm_insert_node_generic(&mm, &node, 2, 0, 0, mode);
> if (err) {
> pr_err("Could not insert the node into the available hole!\n");
> @@ -1998,7 +1988,6 @@ static int __igt_once(unsigned int mode)
> goto err_hi;
> }
>
> -err_node:
> drm_mm_remove_node(&node);
> err_hi:
> drm_mm_remove_node(&rsvd_hi);
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-06-15 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 14:54 [PATCH 1/3] drm/mm: remove unused rb_hole_size() Christian König
2020-06-15 14:54 ` [PATCH 2/3] drm/mm: optimize find_hole() as well Christian König
2020-06-15 16:54 ` Nirmoy [this message]
2020-06-15 14:54 ` [PATCH 3/3] drm/mm: cleanup and improve next_hole_*_addr() Christian König
2020-06-15 16:38 ` Nirmoy
2020-06-15 16:36 ` [PATCH 1/3] drm/mm: remove unused rb_hole_size() Nirmoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=060aa4b7-54ca-1621-4bf2-b018f7da0121@amd.com \
--to=nirmodas@amd.com \
--cc=chris@chris-wilson.co.uk \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox