diff options
| author | mperes <mperes@web> | 2014-10-12 11:06:25 -0700 |
|---|---|---|
| committer | xorg <iki-xorg@freedesktop.org> | 2014-10-12 11:06:25 -0700 |
| commit | fff2a28113c51dcdf19cc53f758afe11f450e812 (patch) | |
| tree | c6a296a94a9ed7c0bae56be25f64391cb4c09213 /Events/XDC2014 | |
| parent | 635d26ee7842fecbd1491254e928f1d01c7d0acb (diff) | |
Diffstat (limited to 'Events/XDC2014')
| -rw-r--r-- | Events/XDC2014/XDC2014PeltonenSynchronization.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Events/XDC2014/XDC2014PeltonenSynchronization.mdwn b/Events/XDC2014/XDC2014PeltonenSynchronization.mdwn index 4abeb233..b4737973 100644 --- a/Events/XDC2014/XDC2014PeltonenSynchronization.mdwn +++ b/Events/XDC2014/XDC2014PeltonenSynchronization.mdwn @@ -12,3 +12,6 @@ Fences are used for synchronizing hardware engine access to buffers. There are t * Currently used on Android (sync fence fd's) I will present some advantages of the explicit sync model, along with some ideas how it could be supported by DRM drivers in a way that is fully compatible with the current implicit sync model. + + +[[Slides|nvidia-explicit-synchronization.pdf]] |