Linux Media Controller development
 help / color / mirror / Atom feed
From: Andres Rodriguez <andresx7@gmail.com>
To: "Christian König" <deathsimple@vodafone.de>,
	"Dave Airlie" <airlied@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
	"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] dma-buf: avoid scheduling on fence status query
Date: Wed, 26 Apr 2017 10:28:49 -0400	[thread overview]
Message-ID: <5c38fa6a-7be1-d2d3-13fd-ec3d527cf021@gmail.com> (raw)
In-Reply-To: <a280488c-8bf0-f0c8-fff4-9f89462ebe34@vodafone.de>



On 2017-04-26 06:13 AM, Christian König wrote:
> Am 26.04.2017 um 11:59 schrieb Dave Airlie:
>> On 26 April 2017 at 17:20, Christian König <deathsimple@vodafone.de>
>> wrote:
>>> NAK, I'm wondering how often I have to reject that change. We should
>>> probably add a comment here.
>>>
>>> Even with a zero timeout we still need to enable signaling, otherwise
>>> some
>>> fence will never signal if userspace just polls on them.
>>>
>>> If a caller is only interested in the fence status without enabling the
>>> signaling it should call dma_fence_is_signaled() instead.
>> Can we not move the return 0 (with spin unlock) down after we enabling
>> signalling, but before
>> we enter the schedule_timeout(1)?
>
> Yes, that would be an option.
>

I was actually arguing with Dave about this on IRC yesterday. Seems like 
I owe him a beer now.

-Andres

> Christian.
>
>>
>> Dave.
>
>

      reply	other threads:[~2017-04-26 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170426013632.4716-1-andresx7@gmail.com>
2017-04-26  2:50 ` [PATCH] dma-buf: avoid scheduling on fence status query Andres Rodriguez
2017-04-26  7:20   ` Christian König
2017-04-26  9:59     ` Dave Airlie
2017-04-26 10:13       ` Christian König
2017-04-26 14:28         ` Andres Rodriguez [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=5c38fa6a-7be1-d2d3-13fd-ec3d527cf021@gmail.com \
    --to=andresx7@gmail.com \
    --cc=airlied@gmail.com \
    --cc=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.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