From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org, dwmw2@infradead.org
Subject: Re: [PATCH 9/9] drm/i915: add bufferless execbuf ioctl
Date: Fri, 04 Sep 2015 12:09:50 -0700 [thread overview]
Message-ID: <55E9EC7E.5080807@virtuousgeek.org> (raw)
In-Reply-To: <20150904173757.GQ2808@nuc-i3427.alporthouse.com>
On 09/04/2015 10:37 AM, Chris Wilson wrote:
> On Fri, Sep 04, 2015 at 09:59:03AM -0700, Jesse Barnes wrote:
>> We just need to pass in an address to execute and some flags, since we
>> don't have to worry about buffer relocation or any of the other usual
>> stuff. Returns a fence to be used for synchronization.
>
> There is no need for a flush+fence as part of the execbuf except for
> when the client requests one (having it optional in the flags as a
> syscall convenience). Just allow the client to inject fences
> when it wants and even then it may just elect to do all fencing itself
> from userspace. Kernel fencing is only interesting for interclient
> operation.
Yeah that's easy enough to add; are you thinking userspace would just be
polling periodically on some ranges? And only requesting fences for
specific batches for blocking purposes?
Jesse
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-09-04 19:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 16:58 [RFC] Page table sharing and bufferless execbuf Jesse Barnes
2015-09-04 16:58 ` [PATCH 1/9] mm: move mmu_find_ops to mmu_notifier.c Jesse Barnes
2015-09-04 16:58 ` [PATCH 2/9] signal: export force_sig_info Jesse Barnes
2015-09-04 16:58 ` [PATCH 3/9] android/sync: add sync_fence_create_dma Jesse Barnes
2015-09-04 16:58 ` [PATCH 4/9] android/sync: hack: enable fence signaling in Android Native Sync implementation Jesse Barnes
2015-09-04 16:58 ` [PATCH 5/9] drm/i915: add create_context2 ioctl Jesse Barnes
2015-09-04 16:59 ` [PATCH 6/9] drm/i915: driver based PASID handling Jesse Barnes
2015-10-07 13:00 ` David Woodhouse
2015-10-07 15:16 ` Jesse Barnes
2015-10-07 16:14 ` Daniel Vetter
2015-10-07 16:28 ` Jesse Barnes
2015-10-07 17:17 ` David Woodhouse
2015-10-07 17:26 ` Jesse Barnes
2015-10-08 8:12 ` Daniel Vetter
2015-10-08 10:28 ` Tomas Elf
2015-10-08 11:29 ` Tomas Elf
2015-10-08 22:46 ` David Woodhouse
2015-10-09 7:28 ` Daniel Vetter
2015-10-09 7:52 ` Daniel Vetter
2015-10-09 7:56 ` David Woodhouse
2015-10-09 8:47 ` Daniel Vetter
2015-10-09 9:07 ` David Woodhouse
2015-10-09 16:20 ` Jesse Barnes
2015-10-08 15:57 ` Chris Wilson
2015-10-09 7:24 ` David Woodhouse
2015-09-04 16:59 ` [PATCH 7/9] drm/i915: add fences to the request struct Jesse Barnes
2015-10-09 13:29 ` David Woodhouse
2015-10-09 16:11 ` Jesse Barnes
2015-09-04 16:59 ` [PATCH 8/9] drm/i915: Android sync points for i915 v4 (obsolete) Jesse Barnes
2015-09-04 16:59 ` [PATCH 9/9] drm/i915: add bufferless execbuf ioctl Jesse Barnes
2015-09-04 17:37 ` Chris Wilson
2015-09-04 19:09 ` Jesse Barnes [this message]
2015-10-08 10:34 ` David Woodhouse
2015-09-04 17:23 ` [RFC] Page table sharing and bufferless execbuf Chris Wilson
2015-09-04 19:08 ` Jesse Barnes
2015-09-26 14:55 ` David Woodhouse
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=55E9EC7E.5080807@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=chris@chris-wilson.co.uk \
--cc=dwmw2@infradead.org \
--cc=intel-gfx@lists.freedesktop.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.