From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Christian_K=c3=b6nig?= Subject: Re: [PATCH] drm/syncobj: add sync obj wait interface. (v6) Date: Wed, 12 Jul 2017 18:45:38 +0200 Message-ID: References: <20170706010409.9373-1-airlied@gmail.com> <899f9bb3-f7c7-ce86-c22b-bb8d262778bf@vodafone.de>

<0c81dd81-e84a-2381-3ce1-e08450929da8@daenzer.net> <2a0f44cc-b893-153c-9852-b1b4855e386e@vodafone.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1622437765==" Return-path: In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: amd-gfx-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "amd-gfx" To: Jason Ekstrand , Dave Airlie Cc: =?UTF-8?Q?Michel_D=c3=a4nzer?= , amd-gfx mailing list , Maling list - DRI developers List-Id: dri-devel@lists.freedesktop.org This is a multi-part message in MIME format. --===============1622437765== Content-Type: multipart/alternative; boundary="------------969E556DC2AD0A062C5BDC99" Content-Language: en-US This is a multi-part message in MIME format. --------------969E556DC2AD0A062C5BDC99 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Am 12.07.2017 um 17:53 schrieb Jason Ekstrand: > [SNIP] > > Is that easier than just waiting in the kernel, I'm not sure how > optimised we need this path to be. > > > I don't think so. I think it's more-or-less the same code regardless > of how it's done. The advantage of doing it in the kernel is that > it's standardized (we don't have to both go write that userspace code) > and it doesn't have the problems stated above. Ok, I'm convinced. The next price question is then how do we do it? I mean writing an IOCTL to wait for a fence to appear is simple, but do we also need to wait for a fence to change? As long as waits don't consume fences that might be rather tricky. Christian. --------------969E556DC2AD0A062C5BDC99 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Am 12.07.2017 um 17:53 schrieb Jason Ekstrand:

[SNIP]

Is that easier than just waiting in the kernel, I'm not sure how
optimised we need this path to be.

I don't think so. I think it's more-or-less the same code regardless of how it's done. The advantage of doing it in the kernel is that it's standardized (we don't have to both go write that userspace code) and it doesn't have the problems stated above.

Ok, I'm convinced. The next price question is then how do we do it?

I mean writing an IOCTL to wait for a fence to appear is simple, but do we also need to wait for a fence to change?

As long as waits don't consume fences that might be rather tricky.

Christian.
--------------969E556DC2AD0A062C5BDC99-- --===============1622437765== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KYW1kLWdmeCBt YWlsaW5nIGxpc3QKYW1kLWdmeEBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9hbWQtZ2Z4Cg== --===============1622437765==--