From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
Gustavo Padovan <gustavo@padovan.org>,
dri-devel@lists.freedesktop.org, daniel.vetter@ffwll.ch,
Zach Reizner <zachr@google.com>,
intel-gfx@lists.freedesktop.org,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH 3/3] drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl)
Date: Tue, 12 Jul 2016 16:23:11 +0200 [thread overview]
Message-ID: <20160712142311.GQ23520@phenom.ffwll.local> (raw)
In-Reply-To: <20160712110403.GQ6157@nuc-i3427.alporthouse.com>
On Tue, Jul 12, 2016 at 12:04:03PM +0100, Chris Wilson wrote:
> On Tue, Jul 12, 2016 at 12:44:17PM +0200, Daniel Vetter wrote:
> > On Mon, Jul 11, 2016 at 04:24:45PM +0100, Chris Wilson wrote:
> > > That doesn't fit the out-of-order unbound nature of the interface. The
> > > interface is just a collection of fences that userspace associates with
> > > the buffer that it may signal at any time. (Having no strict timeline is
> > > an advantage!)
> >
> > Fences on the same timeline are supposed to be signalled in-order. If you
> > want full out-of-order fences then you need to grab a new timeline number
> > for each one. Drivers can and do merge fences on the same timeline and
> > just carry the one with the largest seqno around.
>
> Ugh. Timelines simply don't mean anything everywhere - a very leaky
> abstration.
>
> Nevertheless, a fence_context per vgem_fence would do the trick.
Yeah it's a bit meh, but allocating plenty of them is how we currently
cope with it. I suggested that we have a special FENCE_TIMELINE_UNORDERED
flag (we need it for fence_array too), but that wasn't popular. I still
expect it to happen eventually ;-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-12 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 13:08 drm/vgem fixes and new ioctl for testing prime Chris Wilson
2016-07-11 13:08 ` [PATCH 1/3] drm/vgem: Fix mmaping Chris Wilson
2016-07-11 13:08 ` [PATCH 2/3] drm/vgem: Enable dmabuf interface for export Chris Wilson
2016-07-12 10:45 ` Daniel Vetter
2016-07-11 13:08 ` [PATCH 3/3] drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl) Chris Wilson
2016-07-11 15:10 ` Gustavo Padovan
2016-07-11 15:24 ` Chris Wilson
2016-07-12 10:44 ` Daniel Vetter
2016-07-12 11:04 ` Chris Wilson
2016-07-12 14:23 ` Daniel Vetter [this message]
2016-07-11 14:02 ` ✗ Ro.CI.BAT: failure for series starting with [1/3] drm/vgem: Fix mmaping Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-06-23 14:35 [PATCH 1/3] " Chris Wilson
2016-06-23 14:35 ` [PATCH 3/3] drm/vgem: Attach sw fences to exported vGEM dma-buf (ioctl) Chris Wilson
2016-06-30 15:40 ` Zach Reizner
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=20160712142311.GQ23520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=zachr@google.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.