From: zhoucm1 <zhoucm1-5C7GfCeVMHo@public.gmane.org>
To: "Christian König"
<ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 1/3] drm/amdgpu: use ctx bytes_moved
Date: Tue, 10 Apr 2018 10:34:44 +0800 [thread overview]
Message-ID: <01edccfc-b8ca-7117-feaa-d6ce5aa2f131@amd.com> (raw)
In-Reply-To: <20180409101900.2790-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
On 2018年04月09日 18:18, Christian König wrote:
> Instead of the global (inaccurate) counter.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
> index d7d7ce1507ec..de69ab12bb55 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
> @@ -412,7 +412,6 @@ static bool amdgpu_cs_try_evict(struct amdgpu_cs_parser *p,
> struct amdgpu_bo_list_entry *candidate = p->evictable;
> struct amdgpu_bo *bo = candidate->robj;
> struct amdgpu_device *adev = amdgpu_ttm_adev(bo->tbo.bdev);
> - u64 initial_bytes_moved, bytes_moved;
> bool update_bytes_moved_vis;
> uint32_t other;
>
> @@ -436,18 +435,15 @@ static bool amdgpu_cs_try_evict(struct amdgpu_cs_parser *p,
> continue;
>
> /* Good we can try to move this BO somewhere else */
> - amdgpu_ttm_placement_from_domain(bo, other);
> update_bytes_moved_vis =
> adev->gmc.visible_vram_size < adev->gmc.real_vram_size &&
> bo->tbo.mem.mem_type == TTM_PL_VRAM &&
> bo->tbo.mem.start < adev->gmc.visible_vram_size >> PAGE_SHIFT;
> - initial_bytes_moved = atomic64_read(&adev->num_bytes_moved);
> + amdgpu_ttm_placement_from_domain(bo, other);
> r = ttm_bo_validate(&bo->tbo, &bo->placement, &ctx);
> - bytes_moved = atomic64_read(&adev->num_bytes_moved) -
> - initial_bytes_moved;
> - p->bytes_moved += bytes_moved;
> + p->bytes_moved += ctx.bytes_moved;
> if (update_bytes_moved_vis)
> - p->bytes_moved_vis += bytes_moved;
> + p->bytes_moved_vis += ctx.bytes_moved;
>
> if (unlikely(r))
> break;
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-04-10 2:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 10:18 [PATCH 1/3] drm/amdgpu: use ctx bytes_moved Christian König
[not found] ` <20180409101900.2790-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-04-09 10:18 ` [PATCH 2/3] drm/amdgpu: fix and cleanup cpu visible VRAM handling Christian König
[not found] ` <20180409101900.2790-2-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-04-09 10:52 ` Michel Dänzer
2018-04-10 2:38 ` zhoucm1
2018-04-09 10:19 ` [PATCH 3/3] drm/amdgpu: remove AMDGPU_GEM_CREATE_NO_FALLBACK handling from CS again Christian König
[not found] ` <20180409101900.2790-3-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-04-10 2:43 ` zhoucm1
[not found] ` <11e2b937-9e84-428a-1a90-8752f0dadda4-5C7GfCeVMHo@public.gmane.org>
2018-04-10 9:00 ` Christian König
[not found] ` <94eedefc-bd56-652f-39cf-7331bc5892ea-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-04-10 9:06 ` zhoucm1
2018-04-10 2:34 ` zhoucm1 [this message]
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=01edccfc-b8ca-7117-feaa-d6ce5aa2f131@amd.com \
--to=zhoucm1-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox