All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Jerry (Junwei)" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>,
	"Christian König" <christian.koenig-5C7GfCeVMHo@public.gmane.org>
Cc: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH v2] drm/amdgpu: Reserve shared fence slot in amdgpu_vm_update_directories
Date: Tue, 3 Jul 2018 16:37:21 +0800	[thread overview]
Message-ID: <5B3B35C1.2010408@amd.com> (raw)
In-Reply-To: <78dcd991-2406-59f3-199a-721797a32c2c-otUistvHUpPR7s880joybQ@public.gmane.org>

On 07/03/2018 04:28 PM, Michel Dänzer wrote:
> On 2018-07-03 10:12 AM, Zhang, Jerry (Junwei) wrote:
>>
>> BTW, reservation_object_reserve_shared() will extend the max num as 2
>> times if it's not enough.
>> (default value is 4)
>
> That's an implementation detail and depends on the circumstances. The
> only guarantee is that there's space for at least one fence after
> calling reservation_object_reserve_shared, until
> reservation_object_add_shared_fence is called.

yes, it's a bit more detail discussion about that.
Anyway, it should reserve at least one for shared reservation.
Let's back to the upper level discussion.

Jerry

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

  parent reply	other threads:[~2018-07-03  8:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 16:42 [PATCH] drm/amdgpu: Reserve shared fence slot in amdgpu_vm_update_directories Michel Dänzer
     [not found] ` <20180622164235.30770-1-michel-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-06-25  2:15   ` Zhang, Jerry (Junwei)
     [not found]     ` <5B305042.2060202-5C7GfCeVMHo@public.gmane.org>
2018-06-25  9:08       ` Michel Dänzer
2018-06-25  9:07   ` [PATCH v2] " Michel Dänzer
     [not found]     ` <20180625090717.28522-1-michel-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-06-25  9:45       ` Zhang, Jerry (Junwei)
2018-07-02  9:23       ` Christian König
     [not found]         ` <15c3905c-8e69-9d03-e506-929e4d9176e3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-07-03  1:59           ` Zhang, Jerry (Junwei)
     [not found]             ` <5B3AD88D.2010604-5C7GfCeVMHo@public.gmane.org>
2018-07-03  6:58               ` Christian König
     [not found]                 ` <a95367bc-1181-649d-eca0-64ec0380c6c2-5C7GfCeVMHo@public.gmane.org>
2018-07-03  8:12                   ` Zhang, Jerry (Junwei)
     [not found]                     ` <5B3B2FE9.1000402-5C7GfCeVMHo@public.gmane.org>
2018-07-03  8:28                       ` Michel Dänzer
     [not found]                         ` <78dcd991-2406-59f3-199a-721797a32c2c-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-07-03  8:37                           ` Zhang, Jerry (Junwei) [this message]
2018-07-03  8:42                       ` Christian König
     [not found]                         ` <f6dc6a5b-f6c4-5693-6bad-b2ce29ea54bc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-07-03  9:03                           ` Zhang, Jerry (Junwei)

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=5B3B35C1.2010408@amd.com \
    --to=jerry.zhang-5c7gfcevmho@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=michel-otUistvHUpPR7s880joybQ@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 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.