From: Gustavo Padovan <gustavo@padovan.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: m.b.lankhorst@gmail.com, dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
linaro-mm-sig@lists.linaro.org,
"Alex Deucher" <alexander.deucher@amd.com>
Subject: Re: [PATCH] dma-buf/fence: fix fence_is_later v2
Date: Mon, 29 Feb 2016 19:13:33 -0300 [thread overview]
Message-ID: <20160229221333.GE2479@joana> (raw)
In-Reply-To: <1456761191-8043-1-git-send-email-alexander.deucher@amd.com>
2016-02-29 Alex Deucher <alexdeucher@gmail.com>:
> From: Christian König <christian.koenig@amd.com>
>
> A fence is never later than itself. This caused a bunch of overhead for AMDGPU.
>
> v2: simplify check as suggested by Michel.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> include/linux/fence.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Gustavo
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-02-29 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 15:53 [PATCH] dma-buf/fence: fix fence_is_later v2 Alex Deucher
2016-02-29 22:13 ` Gustavo Padovan [this message]
2016-03-01 8:36 ` Maarten Lankhorst
2016-03-01 8:42 ` Christian König
2016-03-03 12:43 ` Sumit Semwal
-- strict thread matches above, loose matches on Subject: below --
2016-02-23 2:21 Alex Deucher
2016-02-22 19:32 Alex Deucher
2016-02-23 2:04 ` Michel Dänzer
2016-02-29 15:48 ` Daniel Vetter
2016-03-02 3:02 ` Sumit Semwal
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=20160229221333.GE2479@joana \
--to=gustavo@padovan.org \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=m.b.lankhorst@gmail.com \
/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.