From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: amd-gfx mailing list
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"Mao, David" <David.Mao-5C7GfCeVMHo@public.gmane.org>
Subject: Re: libdrm amdgpu semaphores questions
Date: Fri, 2 Dec 2016 09:41:05 +0800 [thread overview]
Message-ID: <5840D131.7090207@amd.com> (raw)
In-Reply-To: <CAPM=9twcZ3eJ4+4ZDr29UGm0Bo7qAYyNdmGSNHqL+G7n7D=7fQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Thanks Dave, got your suggestion.
Regards,
David Zhou
On 2016年12月02日 03:44, Dave Airlie wrote:
> Hi David,
>
> Some one major review suggestion, don't use file descriptors for
> semaphore, as fd's are a limited resource and we don't want to use
> them all up.
>
> You create semaphore objects and use them in a single process without
> them being fds, then when userspace wants to share with another
> process
> you convert the semaphore object to an fd, pass it to the other
> process and have it convert it back into a semaphore object.
>
> Dave.
>
> On 1 December 2016 at 16:11, zhoucm1 <david1.zhou@amd.com> wrote:
>> Hi Dave,
>>
>> As the attached, our Vulkan team is verifying it.
>>
>> Thanks,
>> David Zhou
>>
>>
>> On 2016年12月01日 13:44, Dave Airlie wrote:
>>
>> On 1 Dec. 2016 15:22, "zhoucm1" <david1.zhou@amd.com> wrote:
>>> Yes, the old implementation which is already in upstream libdrm is out of
>>> data, there isn't other user, so we want to drop it when new semaphore is
>>> verified OK.
>> Could you post some patches for the new one? Otherwise I'll have to write
>> one for radv.
>>
>> Dave.
>>> Thanks,
>>> David Zhou
>>>
>>>
>>> On 2016年12月01日 10:36, Mao, David wrote:
>>>> Hi Dave,
>>>> i believe your first attempt is correct.
>>>> The export/import semaphore needs refine of the semaphore implementation.
>>>> We are working on that.
>>>>
>>>> Thanks.
>>>> Best Regards,
>>>> David
>>>>> On 1 Dec 2016, at 10:12 AM, Dave Airlie <airlied@gmail.com> wrote:
>>>>>
>>>>> Hey all,
>>>>>
>>>>> So I've started adding semaphore support to radv but I'm not really
>>>>> sure what the API to the semaphore code is.
>>>>>
>>>>> the Vulkan API is you get a command submission of a number of submit
>>>>> units which have a 0-n wait semaphore, 0-n command buffers and 0-n
>>>>> signal semaphores.
>>>>>
>>>>> Now I'm not sure how I should use the APIs with those.
>>>>>
>>>>> My first attempt is
>>>>>
>>>>> call amdgpu_cs_wait_semaphore on all the wait ones, call the cs submit
>>>>> API, then call the amdgpu_cs_signal_semaphore on all the signal ones?
>>>>>
>>>>> or should I be up front calling wait/signal then submitting the command
>>>>> streams?
>>>>>
>>>>> Also upcoming work requires possibly sharing semaphores between
>>>>> processes, is there any indication how this might be made work with
>>>>> the libdrm_amdgpu semaphore implementation?
>>>>>
>>>>> Thanks,
>>>>> Dave.
>>>>> _______________________________________________
>>>>> 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
>>>
>>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2016-12-02 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 2:12 libdrm amdgpu semaphores questions Dave Airlie
[not found] ` <CAPM=9twrphvnNx99H4r3ROaNaKMKj7uwuii_1Ph57Vv7Z-aFSg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-01 2:36 ` Mao, David
[not found] ` <420B93AA-EBE2-4DB4-B0D0-AE574AEFA22B-5C7GfCeVMHo@public.gmane.org>
2016-12-01 5:17 ` zhoucm1
[not found] ` <583FB287.5050602-5C7GfCeVMHo@public.gmane.org>
2016-12-01 5:44 ` Dave Airlie
[not found] ` <CAPM=9tz2Qv0DXp-Tpfb38b81G1Gbs0MyM4KvUcvj5m+sp3dhoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-01 6:11 ` zhoucm1
[not found] ` <583FBF14.8000506-5C7GfCeVMHo@public.gmane.org>
2016-12-01 9:53 ` Christian König
2016-12-01 17:14 ` Emil Velikov
2016-12-01 19:44 ` Dave Airlie
[not found] ` <CAPM=9twcZ3eJ4+4ZDr29UGm0Bo7qAYyNdmGSNHqL+G7n7D=7fQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-02 1:41 ` zhoucm1 [this message]
[not found] ` <5840D131.7090207-5C7GfCeVMHo@public.gmane.org>
2016-12-02 8:44 ` Christian König
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=5840D131.7090207@amd.com \
--to=david1.zhou-5c7gfcevmho@public.gmane.org \
--cc=David.Mao-5C7GfCeVMHo@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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