From: "Liang, Prike" <Prike.Liang@amd.com>
To: "Zhou, David(ChunMing)" <David1.Zhou@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: RE: [PATCH] ttm: wait mem space if user allow while gpu busy
Date: Tue, 23 Apr 2019 01:45:48 +0000 [thread overview]
Message-ID: <MN2PR12MB35364A346259FD74BD3E1CD7FB230@MN2PR12MB3536.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20190422103836.4300-1-david1.zhou@amd.com>
Acked-by: Prike Liang <Prike.Liang@amd.com>
Thanks,
Prike
-----Original Message-----
From: Chunming Zhou <david1.zhou@amd.com>
Sent: Monday, April 22, 2019 6:39 PM
To: dri-devel@lists.freedesktop.org
Cc: Liang, Prike <Prike.Liang@amd.com>; Zhou, David(ChunMing) <David1.Zhou@amd.com>
Subject: [PATCH] ttm: wait mem space if user allow while gpu busy
heavy gpu job could occupy memory long time, which could lead to other user fail to get memory.
Change-Id: I0b322d98cd76e5ac32b00462bbae8008d76c5e11
Signed-off-by: Chunming Zhou <david1.zhou@amd.com>
---
drivers/gpu/drm/ttm/ttm_bo.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c index 7c484729f9b2..6c596cc24bec 100644
--- a/drivers/gpu/drm/ttm/ttm_bo.c
+++ b/drivers/gpu/drm/ttm/ttm_bo.c
@@ -830,8 +830,10 @@ static int ttm_bo_mem_force_space(struct ttm_buffer_object *bo,
if (mem->mm_node)
break;
ret = ttm_mem_evict_first(bdev, mem_type, place, ctx);
- if (unlikely(ret != 0))
- return ret;
+ if (unlikely(ret != 0)) {
+ if (!ctx || ctx->no_wait_gpu || ret != -EBUSY)
+ return ret;
+ }
} while (1);
mem->mem_type = mem_type;
return ttm_bo_add_move_fence(bo, man, mem);
--
2.17.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-23 1:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 10:38 [PATCH] ttm: wait mem space if user allow while gpu busy Chunming Zhou
2019-04-23 1:45 ` Liang, Prike [this message]
2019-04-23 13:05 ` Christian König
2019-04-23 13:19 ` Zhou, David(ChunMing)
2019-04-23 14:42 ` [PATCH] " Christian König
2019-04-23 15:09 ` Zhou, David(ChunMing)
2019-04-24 7:12 ` [PATCH] " Christian König
2019-04-24 7:17 ` zhoucm1
2019-04-24 7:30 ` Christian König
2019-04-24 7:59 ` zhoucm1
2019-04-24 8:07 ` Christian König
2019-04-24 8:11 ` zhoucm1
2019-04-24 8:59 ` Koenig, Christian
2019-04-24 9:03 ` zhoucm1
2019-04-24 10:03 ` Christian König
2019-04-24 8:01 ` Daniel Vetter
2019-04-24 8:06 ` Koenig, Christian
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=MN2PR12MB35364A346259FD74BD3E1CD7FB230@MN2PR12MB3536.namprd12.prod.outlook.com \
--to=prike.liang@amd.com \
--cc=David1.Zhou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.