On Tue, Jan 23, 2018 at 7:04 PM, Andres Rodriguez <andre...@gmail.com> wrote: > Calling this function will emit a fence signal operation into the > GPU's command stream. > > Signed-off-by: Andres Rodriguez <andre...@gmail.com> > --- > src/gallium/docs/source/context.rst | 31 +++++++++++++++++++++++++++++++ > src/gallium/include/pipe/p_context.h | 6 ++++++ > 2 files changed, 37 insertions(+) > > diff --git a/src/gallium/docs/source/context.rst > b/src/gallium/docs/source/context.rst > index 0ac7340242..459743e739 100644 > --- a/src/gallium/docs/source/context.rst > +++ b/src/gallium/docs/source/context.rst > @@ -567,7 +567,38 @@ by a single pipe_screen and is not shared with another > process. > (i.e. you shouldn't use it to flush caches explicitly if you want to e.g. > use the resource for texturing) > > +Fences > +^^^^^^ > > +``pipe_fence_handle``, and related methods, are used to synchronize > +execution between multiple parties. Examples include CPU <-> GPU > syncrhonization, > +rederer <-> windowing system, multiple external APIs, etc.
synchronization, renderer Marek _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
