All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: "Christian König" <deathsimple@vodafone.de>
Cc: Andres Rodriguez <andresx7@gmail.com>,
	dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] dma-buf: avoid scheduling on fence status query v2
Date: Thu, 27 Apr 2017 18:27:48 -0300	[thread overview]
Message-ID: <20170427212748.GD2568@joana> (raw)
In-Reply-To: <92c9bc96-cf60-f246-a82e-47653472521e@vodafone.de>

2017-04-26 Christian König <deathsimple@vodafone.de>:

> Am 26.04.2017 um 16:46 schrieb Andres Rodriguez:
> > When a timeout of zero is specified, the caller is only interested in
> > the fence status.
> > 
> > In the current implementation, dma_fence_default_wait will always call
> > schedule_timeout() at least once for an unsignaled fence. This adds a
> > significant overhead to a fence status query.
> > 
> > Avoid this overhead by returning early if a zero timeout is specified.
> > 
> > v2: move early return after enable_signaling
> > 
> > Signed-off-by: Andres Rodriguez <andresx7@gmail.com>
> 
> Reviewed-by: Christian König <christian.koenig@amd.com>

pushed to drm-misc-next. Thanks all.

Gustavo

  reply	other threads:[~2017-04-27 21:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 14:46 [PATCH] dma-buf: avoid scheduling on fence status query v2 Andres Rodriguez
2017-04-26 14:46 ` Andres Rodriguez
2017-04-26 14:49 ` Christian König
2017-04-27 21:27   ` Gustavo Padovan [this message]
2017-05-23 23:47     ` [Linaro-mm-sig] " Dave Airlie
2017-05-24 12:21       ` Daniel Vetter
2017-05-24 12:21         ` Daniel Vetter

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=20170427212748.GD2568@joana \
    --to=gustavo@padovan.org \
    --cc=andresx7@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 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.