All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Felix Kuehling <felix.kuehling@amd.com>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>
Cc: "Xu, Feifei" <Feifei.Xu@amd.com>,
	"Koenig, Christian" <Christian.Koenig@amd.com>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/amdkfd: Signal eviction fence on process destruction (v2)
Date: Fri, 6 Mar 2020 10:39:08 +0100	[thread overview]
Message-ID: <4bf7ef97-cb4d-cc6d-e2fe-d41905198cb0@gmail.com> (raw)
In-Reply-To: <53154a08-d2a0-3460-6ef6-b80a2226160b@amd.com>

Yeah, that one looks important. Feel free to add an Acked-by: Christian 
König <christian.koenig@amd.com>.

Regards,
Christian.

Am 05.03.20 um 17:06 schrieb Felix Kuehling:
> [moving to public mailing list]
>
> Thank you. I'll also apply patch 2/2 to amd-staging-drm-next. It's not 
> fixing a memory leak there, but it should make cleanup after process 
> termination more efficient by avoiding delayed delete of BOs.
>
> Regards,
>   Felix
>
> On 2020-03-04 10:46 p.m., Pan, Xinhui wrote:
>> Series is Reviewed-by: xinhui pan <xinhui.pan@amd.com>
>>
>>> 2020年3月5日 05:50,Kuehling, Felix <Felix.Kuehling@amd.com> 写道:
>>>
>>> Otherwise BOs may wait for the fence indefinitely and never be 
>>> destroyed.
>>>
>>> v2: Signal the fence right after destroying queues to avoid unnecessary
>>>     delaye-delete in kfd_process_wq_release
>>>
>>> Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
>>> ---
>>> drivers/gpu/drm/amd/amdkfd/kfd_process.c | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_process.c 
>>> b/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>>> index d5d4660221af..26f7f178b66d 100644
>>> --- a/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>>> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>>> @@ -625,6 +625,11 @@ static void kfd_process_notifier_release(struct 
>>> mmu_notifier *mn,
>>>
>>>     /* Indicate to other users that MM is no longer valid */
>>>     p->mm = NULL;
>>> +    /* Signal the eviction fence after user mode queues are
>>> +     * destroyed. This allows any BOs to be freed without
>>> +     * triggering pointless evictions or waiting for fences.
>>> +     */
>>> +    dma_fence_signal(p->ef);
>>>
>>>     mutex_unlock(&p->mutex);
>>>
>>> -- 
>>> 2.25.1
>>>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      reply	other threads:[~2020-03-06  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200304210637.27283-3-Felix.Kuehling@amd.com>
     [not found] ` <20200304215023.11551-1-Felix.Kuehling@amd.com>
     [not found]   ` <72EFF772-7B30-4BCC-8DC5-E985100C31B8@amd.com>
2020-03-05 16:06     ` [PATCH 2/2] drm/amdkfd: Signal eviction fence on process destruction (v2) Felix Kuehling
2020-03-06  9:39       ` Christian König [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=4bf7ef97-cb4d-cc6d-e2fe-d41905198cb0@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Feifei.Xu@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=felix.kuehling@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 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.